OneSignal
MessagingSend push notifications, email, and SMS through OneSignal and manage the audience behind them: agents create and update users, aliases, and channel subscriptions, build segments, send with templates, schedule or cancel messages, and pull delivery and outcome analytics.
What This Integration Enables
OneSignal is the interrupt channel. Push lands on lock screens, SMS lands in pockets, and unlike email there is no polite inbox between your message and the person. That reach is why the platform is worth automating and why automating it carelessly is expensive: OneSignal's own targeting defaults fall back to the built-in "Subscribed Users" segment, which means an underspecified send is a broadcast to everyone. FlowRunner agents work both sides of that power. They keep the audience true, syncing users, aliases, tags, and email, SMS, and push subscriptions from your systems of record, and they run the sends, from single transactional messages targeted by external ID to scheduled campaigns with templates and delivery optimization. - Transactional sends targeted at one external ID run autonomously; segment-wide sends pause for a person - Send After scheduling keeps Cancel Scheduled Message available as an escape hatch until delivery begins - Templates designed in the dashboard carry brand and styling, so agents supply only targeting and timing - Delivery stats and outcome analytics flow back into the workflow for reporting - Broadcast approval runs through [human-in-the-loop](/concepts/human-in-the-loop) checkpoints with audience counts attached
Without FlowRunner
With FlowRunner
Use Case Scenarios
An audience that mirrors the CRM without an export step
When a contact reaches lifecycle stage customer in [HubSpot](/integrations/hubspot), the agent calls Create User with the CRM id as external_id, adds the email channel with Create Subscription, and sets plan and industry tags through Update User. When the contact's phone number lands, an SMS subscription follows, delivered through the connected [Twilio](/integrations/twilio) number. Onboarding messages then target the external ID directly: transactional, individual, and safe to run without a human in the path.
A quarter of announcements, queued in advance and still cancelable
Product marketing keeps the announcement calendar in [Google Sheets](/integrations/google-sheets). The agent reads the rows, matches each to its dashboard template via List Templates, and presents the batch: audience, template, send time per row. After the owner approves, Send Push with Template queues each with its Send After time. When a launch slips a week, the agent finds the pending message with List Messages and calls Cancel Scheduled Message, then requeues against the new date. The calendar stays software, not a pile of irreversible commitments.
A win-back campaign with the results attached
The agent builds a lapsed-user segment with Create Segment from last-session and purchase-tag filters, and posts the audience size to [Slack](/integrations/slack) for approval. On sign-off it sends the win-back push, then follows the campaign with Get Message for delivery numbers and View Outcomes for session and purchase conversions, posting a close-the-loop summary three days later. The next campaign starts from evidence, and the temporary segment is removed with Delete Segment when the sweep ends.
Human-in-Loop Highlight
Send Push Notification with segment targeting is the send that cannot be recalled: once delivery begins, Cancel Scheduled Message no longer works, and the message is on the lock screens of everyone the targeting matched. OneSignal's fallback behavior raises the stakes, because a send with no explicit targeting defaults to the entire "Subscribed Users" segment. So FlowRunner agents treat every segment-targeted send as a gated operation. The agent assembles targeting, resolves the audience count, and asks: "Win-back push ready. Segment 'lapsed 30 days' matches a five-figure audience; full copy attached. Queue for tomorrow 9am local time?" Only individually targeted transactional messages skip the gate. The distinction is simple: a message to one known person is automation, a message to everyone is a decision.
Agent Capabilities
24 actionsMessages
8- Send Push Notification Sends a push to subscribers, targeted by External IDs, filters, or segments, with scheduling, timezone and last-active delivery optimization, rich media, action buttons, custom data payloads, and throttling. Returns the created message id.
- Send Email Sends an email to email subscribers, targeted by External IDs or segments, with full HTML bodies and optional from-name and from-address overrides.
- Send SMS Sends an SMS to SMS subscribers through your configured Twilio integration, from an SMS-capable number on the connected account.
- Send Push with Template Sends a push using a dashboard-designed template for content and styling; the flow supplies targeting and optional scheduling.
- List Messages Lists sent and scheduled push, email, and SMS messages, newest first, with per-message delivery statistics and source filtering.
- Get Message Retrieves one message with its full definition and delivery outcomes: successful, failed, errored, converted, remaining, and per-platform stats.
- Cancel Scheduled Message Cancels a scheduled message before delivery begins. Messages that have started sending cannot be stopped.
- Get Message History Requests an asynchronous CSV export of the devices a message reached or that clicked it, delivered by emailed download link. Requires the paid Event Streams feature.
Segments
3- List Segments Lists the app's segments, including built-ins like "Subscribed Users", with id, name, activity status, and read-only flag.
- Create Segment Creates a segment from filter conditions such as tags, session count, last session, location, and language, immediately usable for targeting. Available on paid plans.
- Delete Segment Permanently deletes a segment definition by id. Users in the segment are unaffected; built-in read-only segments cannot be deleted.
Users
6- Create User Creates a user with an external_id identity, optional tags, language, and timezone, and optional channel subscriptions. Returns the existing user if the external_id is already known.
- Get User Retrieves a user by alias with their full identity map, properties, and all channel subscriptions with tokens and enabled state.
- Update User Updates a user's properties by alias. Tags merge with existing tags, and deltas can adjust counted properties like session_count and purchase amount.
- Delete User Permanently deletes a user, their identity, properties, and all subscriptions. Cannot be undone; the user receives nothing further.
- Create Alias Adds an alternative identifier such as a CRM id to an existing user. Alias values must be unique per label across the app.
- Delete Alias Removes an alias label from a user without touching the user or their subscriptions. The onesignal_id alias cannot be deleted.
Subscriptions
3- Create Subscription Adds an email address, E.164 SMS number, or device push token to an existing user. Push tokens normally come from the SDK; use this primarily for email and SMS.
- Update Subscription Updates a subscription's token or enabled state. Disabling opts a channel out of messages without deleting it.
- Delete Subscription Permanently deletes a subscription by id, removing that channel address from the user.
Templates
2- List Templates Lists dashboard-created templates, optionally filtered by channel, with ids, names, and timestamps.
- Get Template Retrieves a template's full content, headings, and channel-specific fields. Pairs with Send Push with Template.
App
2- View App Details Retrieves the app's configuration and audience counts, including total and messageable subscribers. Parts of this endpoint require the Organization API key.
- View Outcomes Retrieves aggregated conversion statistics such as click counts, session duration, or custom outcomes over a time range, optionally restricted by platform and attribution model.
Frequently Asked Questions
What can FlowRunner do with OneSignal?
FlowRunner agents can run Send Push Notification, Send Email, and Send SMS in OneSignal, plus 21 more actions.
Does connecting OneSignal to FlowRunner require OAuth?
No. OneSignal connects to FlowRunner with an API key, no OAuth flow required.
Can OneSignal trigger a FlowRunner workflow automatically?
OneSignal doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with OneSignal
$100 in credits. No card required. Connect in minutes.