Per-pair page

Connect OneSignal to Stripe in two minutes.

Real-time triggers from OneSignal, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.

Connect OneSignal and Stripe See reverse direction

Trigger app

OneSignal as the trigger

Workflows fire when something happens in OneSignal.

OneSignal has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Stripe as the action

Workflows do something in Stripe, instantly.

See all 31 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

OneSignal → Stripe

When something happens in OneSignal, do it in Stripe.

0 OneSignal triggers wired to 31 Stripe actions.

Stripe → OneSignal

Or fire it the other way around.

10 Stripe triggers wired to 4 OneSignal actions downstream.

See Stripe → OneSignal →

How it works

Connect OneSignal and Stripe in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize OneSignal and Stripe
Open Tiny Command, authorize OneSignal and Stripe once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a OneSignal trigger
Drop the OneSignal → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/onesignal.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the OneSignal payload into the Stripe inputs.
stripe.cancel-subscription
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about OneSignal + Stripe.

How long does it take to connect OneSignal and Stripe on Tiny Command?

Under two minutes. Authorize OneSignal and Stripe once each, drop the OneSignal trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the OneSignal ↔ Stripe integration real-time?

Yes. Both OneSignal and Stripe expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between OneSignal and Stripe?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Stripe.

What OneSignal events can trigger a Stripe workflow?

Use Tiny Command's universal Webhook trigger to receive OneSignal events, then run any of the 31 Stripe actions downstream.

Do I need a paid plan to use OneSignal with Stripe?

No. There's a free tier that covers most OneSignal+Stripe use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Stripe → OneSignal instead?

Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/onesignal page with the reverse-direction triggers and actions.