Real-time triggers from RazorPay, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in RazorPay.
Workflows do something in Stripe, instantly.
Pair pages are mirrored. Each direction gets its own dedicated page.
3 RazorPay triggers wired to 31 Stripe actions. Most-used pairing: RazorPay Payment Captured → Cancel Subscription.
10 Stripe triggers wired to 4 RazorPay actions downstream.
See Stripe → RazorPay →Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.
Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.
Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.
Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.
Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).
Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).
Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).
Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).
Fires when a refund clears (UPI is sub-minute, cards can take days). For "refund processed → revoke product access, update customer record, log to refund tracking" workflows.
No code, no glue, no half-day setup. Each step is one click.
Open Tiny Command, authorize RazorPay and Stripe once each. Both connections are available to every workflow on your account.
Drop the RazorPay → RazorPay Payment Captured trigger onto the canvas. Tiny Command auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the Stripe → Cancel Subscription action below it. Map fields from the RazorPay payload into the Stripe inputs.
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Free tier available. No credit card. No onboarding call.