- Integrations
- /
- Stripe
- /
- Triggers
- /
- Subscription Cancelled
TriggerStripeReal-timeUpdated May 2026
How do I trigger when a Stripe subscription is cancelled?
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.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Subscription Cancelled
When the matching event happens
when subscription cancelledwhen a subscription is cancelled in stripenew subscription cancelledwatch for subscription cancelledon subscription cancelled
What this trigger returns
for the curiousYou 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}
Output shape
Fields available to downstream nodes.
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 |
Pairs with
Drop these actions after Subscription Cancelled.
FAQ
Questions about Subscription Cancelled.
How does the Subscription Cancelled trigger work in Stripe?
Fires when a subscription is cancelled in Stripe. Use to revoke entitlements, log churn, kick off a win-back campaign, or update your data warehouse.
Is the Subscription Cancelled trigger real-time?
Yes. Subscription Cancelled uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Stripe.
What data does Subscription Cancelled return?
The full event payload from Stripe. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Subscription Cancelled so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Stripe admin permissions to use Subscription Cancelled?
For most Stripe accounts a standard user can authorize the trigger. Some Stripe plans require an admin to enable third-party webhooks. Check Stripe's docs if the trigger fails to register.
More triggers
Other Stripe triggers.
Trigger
Charge Failed
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
TriggerCheckout Completed
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
TriggerNew Customer
Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.
TriggerNew Dispute
Fires when a charge dispute is created in Stripe (chargeback). Critical: route to ops immediately so you can gather evidence before the response window closes.
TriggerInvoice Paid
Fires when an invoice is paid in Stripe. Use to recognise revenue in your accounting system, extend the subscription, or thank the customer.
Build a workflow on this trigger.
One trigger. 31+ downstream actions. Zero glue.