Can Lyro send a push notification through this integration?

No. This toolkit covers users, devices, subscriptions, segments, and outcomes; it exposes no create-notification or send action. Lyro answers in the live channel the customer is already using and updates the OneSignal record so your own campaigns target them correctly.

How does Lyro identify the right OneSignal user?

By alias. View OneSignal User takes an alias label and alias ID, such as an external_id you already set, rather than an email guess. Delete User Alias goes further and requires the user to be identified by one alias while a different alias is the one being removed, which prevents deleting the only identifier on a record.

How is unsubscribing handled if the customer is not in your app?

Update Subscription By Token exists precisely for that case - it enables or disables a subscription using its token when the change is made outside the OneSignal SDK. That means Lyro can honour an opt-out raised over chat, email, or WhatsApp without the customer opening the app.

Does this work across more than one OneSignal app?

Yes, one app at a time. Calls are scoped by app_id: View App returns a specific app's settings, View Segments needs the app_id before it will list, and View Broadcasts and View Outcomes are both per app. Lyro targets the app you name rather than merging several workspaces.

Onesignal user auth MCP integration

Resolves a customer by alias, updates their user and device record, toggles subscriptions by token, and reads segment and outcome data.

Connect Onesignal user auth See all integrations

12actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create or update onesignal user
Lyro creates a new user or modifies subscriptions for an existing OneSignal user. Support teams manage push notification preferences without leaving the chat.
View user unread message count
Lyro retrieves the unread message count for a specific user. Agents diagnose notification issues with real-time counts.
View onesignal user
Lyro retrieves user details by alias label and ID from OneSignal. Teams access user subscription data instantly without manual lookups.

See all 12 actions

How businesses use Onesignal user auth + Lyro

Each card is one request a support team gets, and the Onesignal user auth actions Lyro runs to close it.

Attach the person in chat to their OneSignal record
Lyro looks a customer up by alias label and ID, reads their tags, subscriptions, and identity, and creates or updates the record when the details they give differ from what OneSignal holds.
View OneSignal UserCreate or Update OneSignal UserDelete User Alias
Act on an opt-out the moment a customer asks
Lyro disables the subscription by its token, adjusts the device record it belongs to, and removes the alias that linked it, so a stop request is applied rather than logged for someone to action later.
Update Subscription By TokenEdit OneSignal DeviceDelete User Alias
Answer whether a message actually reached someone
Lyro checks the customer's unread inbox count, lists the app's recent broadcasts, and reads their device record to confirm what was sent and whether it is still waiting to be opened.
View User Unread Message CountView BroadcastsView OneSignal Device
Report on segment size and campaign outcomes
Lyro lists the app's segments, returns the subscriber count for a named one, and pulls outcome metrics filtered by time range, platform, and attribution type.
View SegmentsView OneSignal SegmentView Outcomes

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Onesignal user auth actions it has and picks the ones a request needs.

01
Connect Onesignal user auth
Authorize the Onesignal user auth account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Onesignal user auth actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Onesignal user auth · Lyro

Everything else about Onesignal user auth

Setup, permissions, and the limits of what Lyro can do inside Onesignal user auth.

No. This toolkit covers users, devices, subscriptions, segments, and outcomes; it exposes no create-notification or send action. Lyro answers in the live channel the customer is already using and updates the OneSignal record so your own campaigns target them correctly.

Every action available in Onesignal user auth

All 12 actions your agent can call on Onesignal user auth, straight from the live MCP connection.

Create or update onesignal user
Create a new user or modify the subscriptions associated with an existing user.
Delete user alias
Remove an alias from a OneSignal user.
Edit onesignal device
Update an existing OneSignal device (player) record.
View onesignal segment
Retrieve the subscriber count for a specific OneSignal segment.
Update subscription by token
Update properties on an existing subscription using its token.
View app
Retrieve details for a specific OneSignal app.
View broadcasts
View inbox broadcasts for a OneSignal app.
View onesignal device
Retrieve details for a specific device/player.
View outcomes
View all outcomes associated with a OneSignal app.
View segments
List all segments for an app.
View onesignal user
Retrieve user details by alias label and ID.
View user unread message count
Retrieve the unread message count for a specific user.