MarketingReal-timeUpdated June 2026

OneSignal integration

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.

Connect OneSignal

No credit card required · Set up in under 2 minutes

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

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	Inputs	Open action
Get OneSignal App Statistics	Returns subscribed-user count by platform and recent send aggregates. For "weekly push performance digest" rollup workflows.	0 inputs	View
List OneSignal Notifications	Paginated recent sends with delivery stats. For "which notifications got the most engagement" analysis.	1 input	View
Create OneSignal Notification	Alias for Send Push Notification — creates a push send. For external-event-driven push workflows.	5 inputs	View
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.	4 inputs	View

Recipes

Pre-built OneSignal workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

OneSignal → Slack alerts

AI-triage every OneSignal event, ping the right channel only when it matters.

OneSignal → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

OneSignal → Notion database

Turn OneSignal into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect OneSignal once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every OneSignal field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

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?

Open the Tiny Command workflow builder, drop in a OneSignal node, and click Connect. Authorize OneSignal once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What OneSignal triggers does Tiny Command support?

Tiny Command focuses on outbound actions for OneSignal today. Use Tiny Command's universal Webhook or Schedule trigger to start OneSignal workflows, then run any OneSignal action you need.

What OneSignal actions can I run from a workflow?

4 OneSignal actions are available out of the box, covering marketing operations like "Get OneSignal App Statistics". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the OneSignal integration real-time?

OneSignal actions execute synchronously inside your workflow. Tiny Command waits for OneSignal's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use OneSignal with Tiny Command?

No. Every OneSignal trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any OneSignal API endpoint directly.

How much does the OneSignal integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The OneSignal integration itself has no per-app surcharge.