- Home
- Resources
- Integrations
- OneSignal
Claude OneSignal connectorWhat Claude can do in your OneSignal account.
The Claude OneSignal connector exposes 29 tools. 15 read your messages, users, segments, templates and stats, 14 change them or send a message, and 0 are left undocumented. Below: what Claude can send, what it checks with you first, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your OneSignal
OneSignal sends push notifications, emails, SMS and in-app messages. With the connector, the everyday checks move into the conversation: you ask Claude how last night's campaign delivered, who a given user is subscribed as, or which segment a filter would hit, and it answers from your OneSignal apps, then acts if you ask it to.
Read a campaign's results without the dashboard. A lifecycle marketer asks how yesterday's push performed. Claude lists recent notifications with list_messages, then opens delivery stats with view_message and outcome figures with view_outcomes.
Sort out one user's record. Support says a customer gets no emails. Claude finds the person with view_user, checks identities, then can add an email subscription with create_subscription or move one to the right user with transfer_subscription.
Send to a segment once it is right. Claude can build the audience with create_segment, prepare a template with create_template, and send through send_message, which OneSignal flags as high-impact.
What Claude will not do on its own: nothing goes out on a schedule or when a user signs up, since a connector acts only while you talk to it. It also stays within the apps your OneSignal login already manages. For a message fired automatically by an event, the OneSignal Make integration covers scenarios that run without anyone typing. The two do different jobs; the Integrations hub lists the rest.
Five words before you connect
The vocabulary of this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector gives Claude. Claude picks the tools it needs on its own, and the directory lists them by name.
- Authorization
- OneSignal's own sign-in screen, where you approve Claude's access. It is granted once, per person, and can be withdrawn later.
- Approval
- The confirmation Claude waits for before it goes ahead with something that alters your account or sends a message, shown in the chat.
- MCP
- The shared standard connectors rely on. It is what lets an assistant like Claude talk to an outside service such as OneSignal.
Connect OneSignal to Claude in three steps
- 01
Find OneSignal in Claude
Open Claude's settings, go to Customize, then Connectors, and look for OneSignal in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first, then each member signs in individually.
- 02
Start the connection
Click Connect on the OneSignal row and log in on the page OneSignal opens itself. OneSignal notes that you enter no app ID or API key. If the link breaks, Disconnect and connect again.
- 03
Approve the access screen
Read OneSignal's screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. It may list more rights than Claude uses day to day; asking before each action stays the default.
The 29 tools of the Claude OneSignal connector
OneSignal gives Claude 29 tools: 15 that read your account, 14 that change something in it.
Two groups here: what Claude reads and what it changes or sends. Every tool on the sheet is described by OneSignal. Names stay exactly as Claude shows them.
- 15 read
- 14 write
Tools index
What Claude reads (15)
15 toolsFifteen tools that look at messages, users, segments, templates and results, or export them to a file, without altering anything.
export_audience_activity_csv
Produces a CSV file of the audience activity behind a notification, so you can analyze who received it and what they did outside OneSignal.
export_subscriptions_csv
Exports your subscriptions to a CSV file: a snapshot of the push, email and SMS channels registered in the app.
get_segment
Opens one segment and shows its filters, so Claude can explain in plain words who falls inside it.
get_template
Displays one message template with its content, so Claude can review wording or spot what needs fixing before anyone reuses it.
get_user_identity
Retrieves the identity aliases attached to a user, such as your own customer ID alongside OneSignal's.
get_user_identity_by_subscription
Works the other way round: starting from a subscription ID, it returns the identity of the user who owns it.
list_messages
Lists the notifications recently sent from an app, which gives Claude the starting point for any delivery question.
list_segments
Returns the segments defined in an app, so Claude knows which audiences already exist before suggesting a new one.
list_templates
Lists the message templates saved in an app, across channels, so you can see what is ready to reuse.
onesignal_config
Shows the configuration of the OneSignal connection itself. It concerns the service's setup, not your campaigns or users.
onesignal_health
Checks that the OneSignal service answers. OneSignal suggests it as the first read-only test after connecting.
onesignal_reference_overview
Returns OneSignal's own reference summary of the tools it offers, which helps Claude pick the right one for a request.
view_message
Opens one notification with its details and delivery statistics, so Claude can tell you how it performed and where it fell short, figures included.
view_outcomes
Reads OneSignal's outcome analytics, the results measured after messages were delivered, and reports them back in the conversation.
view_user
Finds a user by alias and shows the record, including the subscriptions attached to it.
What Claude changes or sends (14)
14 toolsFourteen tools that alter users, subscriptions, segments or templates, or send a message. Only send_message has a documented confirmation; the others follow the general rule.
create_alias_by_subscription
Approval: see the ruleAdds identity aliases to a user, reaching that user through one of their subscription IDs.
create_or_update_alias
Approval: see the ruleAdds a new identity alias to a user or corrects an existing one, working from the user directly.
create_segment
Approval: see the ruleBuilds a segment from audience filters, ready to target in a campaign.
create_subscription
Approval: see the ruleAttaches a new push, email or SMS subscription to a user, giving them one more way to be reached.
create_template
Approval: see the ruleSaves a new message template in the app, which later campaigns can reuse.
create_user
Approval: see the ruleRegisters a new user with properties, and OneSignal describes attaching email, SMS or push subscriptions to them at the same time.
send_message
Asks you firstSends a push notification, an email or an SMS. OneSignal validates the targeting first: one targeting method at a time, and capped filters.
transfer_subscription
Approval: see the ruleMoves a subscription from one user to another, for instance when a device changed hands.
unsubscribe_email
Approval: see the ruleUnsubscribes an email address so it stops receiving your email messages.
update_segment
Approval: see the ruleChanges the filters or settings of an existing segment, which alters who future campaigns reach.
update_subscription
Approval: see the ruleModifies an existing subscription, starting from its subscription ID, for example to correct a channel that no longer works.
update_subscription_by_token
Approval: see the ruleMakes the same kind of change to a subscription, but finds it through its token instead of its ID.
update_template
Approval: see the ruleRewrites an existing template, so every campaign built on it afterwards uses the new version.
update_user
Approval: see the ruleUpdates a user's properties, such as tags or language, which in turn affects which segments they fall into.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. For OneSignal, one tool also carries its own warning: send_message.
OneSignal marks send_message as a high-impact action, so compatible clients such as Claude may ask for confirmation before running it, and OneSignal advises reviewing every send request before approving it. No other tool has a documented prompt of its own. On Team and Enterprise workspaces, owners decide whether a member may skip the prompt for some actions, and can restrict a connector for the whole organization. Claude also works with the rights of the person who connected: the connection follows that OneSignal user's permissions and nothing wider.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer for one connector is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. For the live state of this one, the OneSignal sheet in the official directory is the place to look. OneSignal adds that its side of the connection costs nothing extra, though calls count toward your normal API usage.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no message leaves when a user signs up or a cart is abandoned.
Everything here comes from OneSignal's documentation and the directory sheet: no Claude help article covers this connector. The tool list is an observed floor, and the two sources do not even count the same tools. The partner badge is not a security audit, and Anthropic says on every sheet that it neither picks a publisher's tools nor guarantees their behavior. Connect it knowing it comes from OneSignal.
How many tools does the OneSignal connector expose?
- Claude directory sheet ↗September 2026Lists 29 tools by name, the ones this page documents.
- OneSignal documentation ↗September 2026The server supports 43 tools across 11 categories, including live activities, custom events and email deliverability.
What this page followsNeither is out of date: the documentation describes OneSignal's server, the sheet shows what Claude lists. This page covers the 29 tools on the sheet. The other 14 may or may not appear on your account; once connected, Claude lists the tools it actually has.
Need help connecting OneSignal to Claude?
A person reads every message.

