Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect OneSignal to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (15)

15 tools

Fifteen 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.

When it helps
an analyst wants the raw audience data of one campaign in a spreadsheet.
Watch out
it counts against your normal OneSignal API usage, like every call here.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

export_subscriptions_csv

Exports your subscriptions to a CSV file: a snapshot of the push, email and SMS channels registered in the app.

When it helps
you need a list of subscribers for an audit or a migration.
Watch out
the file holds personal data; decide where it goes before asking for it.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

get_segment

Opens one segment and shows its filters, so Claude can explain in plain words who falls inside it.

When it helps
a campaign reached fewer people than planned and you want to see how the audience is defined, filter by filter.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

get_template

Displays one message template with its content, so Claude can review wording or spot what needs fixing before anyone reuses it.

When it helps
you want a second pair of eyes on the welcome email before it goes out again.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

get_user_identity

Retrieves the identity aliases attached to a user, such as your own customer ID alongside OneSignal's.

When it helps
you have a customer number from your CRM and want to confirm it matches the right OneSignal user before touching anything.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

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.

When it helps
a delivery report shows a subscription ID and you need to know which customer it belongs to.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

list_messages

Lists the notifications recently sent from an app, which gives Claude the starting point for any delivery question.

When it helps
you want to know what went out this week before looking at one campaign in detail.
Watch out
it covers recent notifications, not your full history.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

list_segments

Returns the segments defined in an app, so Claude knows which audiences already exist before suggesting a new one.

When it helps
you suspect two teams built near-identical segments and want the full list side by side before cleaning up.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

list_templates

Lists the message templates saved in an app, across channels, so you can see what is ready to reuse.

When it helps
you start a new campaign and want to check whether a template close to it already exists in the app.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

onesignal_config

Shows the configuration of the OneSignal connection itself. It concerns the service's setup, not your campaigns or users.

When it helps
support asks you to confirm how the connection is set up while you troubleshoot a failing request on your side.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

onesignal_health

Checks that the OneSignal service answers. OneSignal suggests it as the first read-only test after connecting.

When it helps
you just connected and want proof that the link works before asking anything real.
Watch out
a healthy result only proves the link; app access can still need enabling.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

onesignal_reference_overview

Returns OneSignal's own reference summary of the tools it offers, which helps Claude pick the right one for a request.

When it helps
you are new to the connector and want a plain overview of what it can handle before your first real request.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

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.

When it helps
yesterday's promo email looks weak and you want the delivery numbers before drawing conclusions.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

view_outcomes

Reads OneSignal's outcome analytics, the results measured after messages were delivered, and reports them back in the conversation.

When it helps
you want to know whether a campaign led to the outcome you track, not just to opens and clicks.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

view_user

Finds a user by alias and shows the record, including the subscriptions attached to it.

When it helps
support passes on a complaint and you want to see every channel that customer is reachable on.
Watch out
you need an alias to search by, such as your own customer ID.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

What Claude changes or sends (14)

14 tools

Fourteen 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 rule

Adds identity aliases to a user, reaching that user through one of their subscription IDs.

What Claude asks for
no confirmation is described for this tool; the general approval rule below applies.
When it helps
you only have a device's subscription ID and need to link it to your internal customer ID.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

create_or_update_alias

Approval: see the rule

Adds a new identity alias to a user or corrects an existing one, working from the user directly.

What Claude asks for
nothing tool-specific is documented; the general rule covers it.
When it helps
your CRM changed its customer IDs and OneSignal records must follow.
Watch out
a wrong alias links messages to the wrong person.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

create_subscription

Approval: see the rule

Attaches a new push, email or SMS subscription to a user, giving them one more way to be reached.

What Claude asks for
the general approval rule below, since no source details this tool.
When it helps
a customer gives their phone number at checkout and should now receive SMS.
Watch out
check the customer agreed to that channel first.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

create_user

Approval: see the rule

Registers a new user with properties, and OneSignal describes attaching email, SMS or push subscriptions to them at the same time.

What Claude asks for
nothing specific is documented; the general approval rule covers it.
When it helps
a B2B client joins by contract and never went through the app sign-up flow.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

send_message

Asks you first

Sends a push notification, an email or an SMS. OneSignal validates the targeting first: one targeting method at a time, and capped filters.

What Claude asks for
OneSignal marks this as a high-impact action, so Claude may ask you to confirm before it goes out.
When it helps
the segment and template are ready and you want the campaign sent now.
Watch out
once sent, a message cannot be recalled; read the prompt carefully.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

transfer_subscription

Approval: see the rule

Moves a subscription from one user to another, for instance when a device changed hands.

What Claude asks for
no confirmation is described for this tool; the general rule below applies.
When it helps
two customer records were merged and the phone subscription sits on the wrong one.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

update_segment

Approval: see the rule

Changes the filters or settings of an existing segment, which alters who future campaigns reach.

What Claude asks for
no prompt specific to this tool is published; the general approval rule below is what covers it.
When it helps
the segment of active users should now exclude people who churned last quarter.
Watch out
campaigns already aimed at it will reach a different audience.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

update_subscription

Approval: see the rule

Modifies an existing subscription, starting from its subscription ID, for example to correct a channel that no longer works.

What Claude asks for
no source describes a confirmation; the default approval rule applies.
When it helps
a customer's email subscription carries an outdated address that needs correcting.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

update_subscription_by_token

Approval: see the rule

Makes the same kind of change to a subscription, but finds it through its token instead of its ID.

What Claude asks for
the general approval rule, since this tool has no documented prompt of its own.
When it helps
your app only stores push tokens and you need to fix a subscription from one of them.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

update_user

Approval: see the rule

Updates a user's properties, such as tags or language, which in turn affects which segments they fall into.

What Claude asks for
nothing specific is documented; the general approval rule below covers it.
When it helps
a customer switched their preferred language and should get messages in it from now on.

Sourcedocumentation.onesignal.com · September 30, 2026 ↗

Approvals

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.

Plans

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.

Limits

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.

Two official sources disagree

How many tools does the OneSignal connector expose?

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

Need help connecting OneSignal to Claude?

A person reads every message.

FAQ

Questions about the Claude OneSignal connector

01What can Claude do with the OneSignal connector?
Claude can read and run your OneSignal messaging from a conversation. Fifteen tools read recent notifications, delivery stats, outcomes, users, identities, segments and templates, run a health check, and export subscriptions or audience activity to CSV. Fourteen more act: creating and updating users, aliases and subscriptions, unsubscribing an email, moving a subscription, creating and editing segments and templates, and sending a push, email or SMS. OneSignal documents every tool on the directory sheet.
02Can Claude send notifications or delete things in OneSignal?
Claude can send: send_message delivers a push notification, an email or an SMS, after OneSignal validates the targeting. It can also create and edit users, subscriptions, segments and templates, move a subscription to another user and unsubscribe an email address. None of the documented tools is described as deleting a user, a segment or a template. OneSignal treats sending as the high-impact action of the list and asks that every send request be reviewed before approval.
03Does Claude ask before it sends a OneSignal message?
For sending, OneSignal says yes in principle: it flags send_message as the high-impact tool of the list, and says clients like Claude may request your confirmation first. For the other changes, no tool-specific prompt is documented, and Claude's default rule applies: it asks before each action it takes on an account for someone. On Team and Enterprise workspaces, owners decide whether members may skip that prompt for some actions, and can close the writing side entirely.
04Which Claude plans is the OneSignal connector available on?
No official source says so for a single connector: none of the 819 directory sheets shows plan availability. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and that on Team and Enterprise an Owner or Primary Owner enables a connector for the organization first. OneSignal says its own side is free, with calls counted in your usual API limits. For this connector's live state, check its directory sheet.
05Can Claude see every app in our OneSignal organization?
It sees what your OneSignal login can manage, which may be several apps, and nothing beyond. OneSignal says the connection follows the permissions of the user who authorized it, and revoking it does not affect other members. You can review or revoke it under Settings, Account settings, Connected apps. During the open beta, an app may also need enabling before its non-utility tools become available, even if your login can already see it.
06Why does the OneSignal documentation list tools Claude does not show?
Because the two sources count different things. OneSignal's documentation says its server supports 43 tools across 11 categories, including live activities, custom events and email deliverability checks. The Claude directory sheet lists 29, and this page documents those. The other 14 may or may not appear on your account. Once the connector is on, Claude lists the tools it really has, which is the answer that counts for your own account.
07Claude or an automation tool for OneSignal?
They do different jobs, so there is no ranking here. Claude suits one-off work in a conversation: checking why a campaign underperformed, fixing a customer's subscriptions, preparing and sending a message after you review it. An automation tool sends by itself when something happens, such as a welcome push the moment someone signs up, with nobody in the loop. If a person decides each time, use Claude; if an event should trigger the message, automate it.