Short answer: Drop the "Stripe → Charge Failed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Stripe, 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": 100,"status": "failed","created": 1778804246,"currency": "usd","customer": null,"event_id": "evt_xxx","livemode": false,"charge_id": "ch_xxx","event_type": "charge.failed","occurred_at": 1778804246,"failure_code": "card_declined","receipt_email": null,"payment_intent": "pi_xxx","payment_method": "pm_xxx","failure_message": "Your card was declined."}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| amount | number | 100 |
| status | string | "failed" |
| created | number | 1778804246 |
| currency | string | "usd" |
| customer | null | null |
| event_id | string | "evt_xxx" |
| livemode | boolean | false |
| charge_id | string | "ch_xxx" |
| event_type | string | "charge.failed" |
| occurred_at | number | 1778804246 |
| failure_code | string | "card_declined" |
| receipt_email | null | null |
| payment_intent | string | "pi_xxx" |
| payment_method | string | "pm_xxx" |
| failure_message | string | "Your card was declined." |
One trigger. 31+ downstream actions. Zero glue.