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