Short answer: Drop the "Stripe → New Subscription" 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.
{"status": "active","created": 1778804246,"currency": "usd","customer": "cus_xxx","event_id": "evt_xxx","livemode": false,"event_type": "customer.subscription.created","occurred_at": 1778804246,"latest_invoice": "in_xxx","subscription_id": "sub_xxx","collection_method": "charge_automatically","current_period_end": 1781396246,"cancel_at_period_end": false,"current_period_start": 1778804246}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| status | string | "active" |
| created | number | 1778804246 |
| currency | string | "usd" |
| customer | string | "cus_xxx" |
| event_id | string | "evt_xxx" |
| livemode | boolean | false |
| event_type | string | "customer.subscription.created" |
| occurred_at | number | 1778804246 |
| latest_invoice | string | "in_xxx" |
| subscription_id | string | "sub_xxx" |
| collection_method | string | "charge_automatically" |
| current_period_end | number | 1781396246 |
| cancel_at_period_end | boolean | false |
| current_period_start | number | 1778804246 |
One trigger. 31+ downstream actions. Zero glue.