Short answer: Drop the "RazorPay → RazorPay Refund Processed" 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.
{"amount": 50000,"status": "processed","currency": "INR","refund_id": "rfnd_abc123def456","payment_id": "pay_abc123def456","speed_processed": "normal"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| amount | number | 50000 |
| status | string | "processed" |
| currency | string | "INR" |
| refund_id | string | "rfnd_abc123def456" |
| payment_id | string | "pay_abc123def456" |
| speed_processed | string | "normal" |
One trigger. 4+ downstream actions. Zero glue.