Short answer: Drop the "Stripe → Checkout Completed" 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.
{"id": "cs_123","mode": "payment","currency": "usd","customer": "cus_456","amount_total": 4999,"customer_email": "buyer@example.com","payment_status": "paid"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | string | "cs_123" |
| mode | string | "payment" |
| currency | string | "usd" |
| customer | string | "cus_456" |
| amount_total | number | 4999 |
| customer_email | string | "buyer@example.com" |
| payment_status | string | "paid" |
One trigger. 31+ downstream actions. Zero glue.