Per-pair page

Connect Stripe to Msg91 in two minutes.

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

Connect Stripe and Msg91 See reverse direction

Trigger app

Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →

Action app

Msg91 as the action

Workflows do something in Msg91, instantly.

Msg91 List ItemsAPI

Both directions

Pick the way that fits your stack.

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

Stripe → Msg91

When something happens in Stripe, do it in Msg91.

10 Stripe triggers wired to 1 Msg91 actions. Most-used pairing: Charge Failed → Msg91 List Items.

Msg91 → Stripe

Or fire it the other way around.

0 Msg91 triggers wired to 31 Stripe actions downstream.

Use any trigger in the catalog as the upstream.

See Msg91 → Stripe →

Popular pairings

Common Stripe → Msg91 workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 3 of 10 combinations

When charge failed in Stripe, msg91 list items in Msg91.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When checkout completed in Stripe, msg91 list items in Msg91.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When new customer in Stripe, msg91 list items in Msg91.

Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.

How it works

Connect Stripe and Msg91 in five steps.

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

1
Connect
Authorize Stripe and Msg91
Open Tiny Command, authorize Stripe and Msg91 once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Stripe trigger
Drop the Stripe → Charge Failed trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/stripe.trigger-charge-failed
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 Msg91 action
Drop the Msg91 → Msg91 List Items action below it. Map fields from the Stripe payload into the Msg91 inputs.
msg91.list
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 Stripe + Msg91.

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

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

Is the Stripe ↔ Msg91 integration real-time?

Yes. Both Stripe and Msg91 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 Stripe and Msg91?

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 Msg91.

What Stripe events can trigger a Msg91 workflow?

Any of the 10 Stripe triggers, including "Charge Failed". Each fires in real time when the matching event happens in Stripe.

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

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

What if I want Msg91 → Stripe instead?

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

Other apps that pair well with Stripe.

Stripe + Gmail

Stripe + Slack

Communication

Stripe + Google Sheets

Spreadsheets & Databases