Short answer: Drop the "RazorPay → RazorPay Payment Failed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in RazorPay, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"id": "pay_fail123def456","email": "customer@example.com","amount": 30000,"method": "card","status": "failed","currency": "INR","error_description": "Payment was declined by the bank"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | string | "pay_fail123def456" |
| string | "customer@example.com" | |
| amount | number | 30000 |
| method | string | "card" |
| status | string | "failed" |
| currency | string | "INR" |
| error_description | string | "Payment was declined by the bank" |
One trigger. 4+ downstream actions. Zero glue.