ActionOneSignalUpdated September 2026

How do I create a OneSignal push notification?

Short answer: You can create onesignal notification in OneSignal by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the OneSignal Create OneSignal Notification action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create OneSignal Notification in OneSignal — start free All 4 OneSignal actions

Create OneSignal Notification in OneSignal — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Title title	string	Required	–
Message message	string	Required	–
Click URL url	string	Optional	A fully qualified URL (https://...) for the click url.
Included Segments included_segments	array	Optional	Default: ["Subscribed Users"]
Specific External User IDs include_external_user_ids	array	Optional	–

Sample request

{
  "title": "{{trigger.title}}",
  "message": "{{trigger.message}}",
  "url": "e.g. https://example.com/path",
  "included_segments": "{{trigger.included_segments}}",
  "include_external_user_ids": "{{trigger.include_external_user_ids}}"
}

Returns

{
  "id": "notif_abc",
  "recipients": 1234,
  "external_id": null
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create OneSignal Notification.

Any of these apps can fire this action as part of a workflow.

Google Sheets → OneSignal

2 Google Sheets triggers

HubSpot → OneSignal

18 HubSpot triggers

FAQ

Questions about Create OneSignal Notification.

What does the Create OneSignal Notification action do in OneSignal?

Alias for Send Push Notification — creates a push send. For external-event-driven push workflows.

What inputs does Create OneSignal Notification require?

Required: Title, Message. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if OneSignal returns an error?

The run history shows the failed step with its input and the error message OneSignal returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create OneSignal Notification support batch operations?

Run Create OneSignal Notification inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within OneSignal's rate limits.

More actions

Other OneSignal actions.

Action

Get OneSignal App Statistics

Returns subscribed-user count by platform and recent send aggregates. For "weekly push performance digest" rollup workflows.

Action

List OneSignal Notifications

Paginated recent sends with delivery stats. For "which notifications got the most engagement" analysis.

Action

Send Push Notification

Sends a push to a specified audience — user IDs, segments, or in-call filter rules. The base hook for "external event → push to mobile users matching X criteria" workflows.

Create OneSignal Notification in OneSignal — start free