OneSignal
OneSignal cross-platform push notifications
OneSignal is the cross-platform push-notification service — web push, iOS push, Android push, in-app messages, and email and SMS — used by mobile apps and web apps that want a single delivery infrastructure rather than integrating with FCM, APNS, and web-push separately. Tiny Command exposes three actions, no triggers (OneSignal emits delivery events via webhooks configured per-app in the dashboard; point at a Tiny Command webhook trigger): Send Push Notification (target by user external_id, by player_id, by segment, by filters like "users in country X who haven't opened in 7 days"), List Notifications (recent sends with delivery stats), Get App Statistics (subscribed-user count by platform, recent send aggregates). The connection uses a OneSignal REST API key + App ID from Settings → Keys & IDs. The Send Push Notification action supports rich payloads — large images, action buttons, deep-link URLs, custom data passed to the app. Segment-targeted sends use OneSignal's audience-segmentation rules; for ad-hoc targeting, the filters parameter is the in-call query.
Do anything OneSignal can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get OneSignal App Statistics | Returns subscribed-user count by platform and recent send aggregates. For "weekly push performance digest" rollup workflows. |
| List OneSignal Notifications | Paginated recent sends with delivery stats. For "which notifications got the most engagement" analysis. |
| 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 | Alias for Send Push Notification — creates a push send. For external-event-driven push workflows. |
Pre-built OneSignal workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect OneSignal once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every OneSignal field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the OneSignal integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect OneSignal to Tiny Command?
What OneSignal triggers does Tiny Command support?
What OneSignal actions can I run from a workflow?
Is the OneSignal integration real-time?
Do I need to write code to use OneSignal with Tiny Command?
How much does the OneSignal integration cost?
More marketing apps people connect.
Same category as OneSignal, ordered by how often teams pair them. Hover the carousel to pause.
Do more with OneSignal.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
