Connect RazorPay to Airtable in two minutes.
Real-time triggers from RazorPay, ready-made actions in Airtable. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in RazorPay.
- RazorPay Payment CapturedWebhook
- RazorPay Payment FailedWebhook
- RazorPay Refund ProcessedWebhook
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in RazorPay, do it in Airtable.
3 RazorPay triggers wired to 9 Airtable actions. Most-used pairing: RazorPay Payment Captured → Create Record.
Or fire it the other way around.
2 Airtable triggers wired to 4 RazorPay actions downstream.
See Airtable → RazorPay →Common RazorPay → Airtable workflows.
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.
Connect RazorPay and Airtable in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize RazorPay and Airtable
Open TinyCommand, authorize RazorPay and Airtable once each. Both connections are available to every workflow on your account.
- 2TriggerPick a RazorPay trigger
Drop the RazorPay → RazorPay Payment Captured trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/razorpay.trigger-payment-captured - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Airtable action
Drop the Airtable → Create Record action below it. Map fields from the RazorPay payload into the Airtable inputs.
airtable.create-record - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
