Short answer: Drop the "Stripe → New Customer" 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.
{"name": "TC Test","email": "tc@example.com","phone": null,"balance": 0,"created": 1778804246,"currency": null,"event_id": "evt_xxx","livemode": false,"delinquent": false,"event_type": "customer.created","customer_id": "cus_xxx","description": null,"occurred_at": 1778804246}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| name | string | "TC Test" |
| string | "tc@example.com" | |
| phone | null | null |
| balance | number | 0 |
| created | number | 1778804246 |
| currency | null | null |
| event_id | string | "evt_xxx" |
| livemode | boolean | false |
| delinquent | boolean | false |
| event_type | string | "customer.created" |
| customer_id | string | "cus_xxx" |
| description | null | null |
| occurred_at | number | 1778804246 |
One trigger. 31+ downstream actions. Zero glue.