Short answer: Drop the "Stripe → New Dispute" 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": 500,"charge": "ch_xxx","reason": "fraudulent","status": "needs_response","created": 1778804246,"currency": "usd","event_id": "evt_xxx","livemode": false,"dispute_id": "du_xxx","event_type": "charge.dispute.created","occurred_at": 1778804246,"payment_intent": "pi_xxx","evidence_due_by": 1779504246}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| amount | number | 500 |
| charge | string | "ch_xxx" |
| reason | string | "fraudulent" |
| status | string | "needs_response" |
| created | number | 1778804246 |
| currency | string | "usd" |
| event_id | string | "evt_xxx" |
| livemode | boolean | false |
| dispute_id | string | "du_xxx" |
| event_type | string | "charge.dispute.created" |
| occurred_at | number | 1778804246 |
| payment_intent | string | "pi_xxx" |
| evidence_due_by | number | 1779504246 |
One trigger. 31+ downstream actions. Zero glue.