Short answer: Drop the "OneSignal → Send Push Notification" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Title headings | string | Required | Title |
Message contents | string | Required | Message |
Segments included_segments | string | Optional | Target audience segment |
Launch URL url | url | Optional | A fully qualified URL (https://...) for the launch url. |
{"headings": "{{trigger.headings}}","contents": "{{trigger.contents}}","included_segments": "{{trigger.included_segments}}","url": "e.g. https://example.com/path"}
{"id": "notif123","recipients": 5000,"external_id": null}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.