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.
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 | – |
{"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}}"}
{"id": "notif_abc","recipients": 1234,"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.