The moment it happens
Hear when a customer cancels
When a subscription is cancelled, you get the customer and plan straight away.
- Runs
- The moment it happens
- Apps
- Stripe
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: when a Stripe subscription is cancelled, Slack me the customer's name, email and plan.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A subscription business loses a customer on a Tuesday afternoon and finds out in the monthly revenue review. By then the account manager who could have called, offered a discount or asked what went wrong has no context left, and the customer has already moved to a competitor. For a company with a few hundred high-value accounts, a single quiet cancellation can be a four-figure annual loss.
The moment Stripe sends a customer.subscription.deleted event, ClickRuntime looks up the customer to get their name, email and plan, then posts a message to your Slack channel. The people who own retention hear about it while the customer is still reachable and the decision is fresh.
It works well for B2B teams with a handful of key accounts, and for founders who still reach out personally to people who leave.
What you get out of it
A save attempt becomes possible
Calling within hours of a cancellation gives you a real chance at winning someone back, or at least learning the reason. A week later the customer has usually settled on an alternative.
High-value losses are never a surprise
The alert includes the plan, so a cancelled enterprise subscription stands out from a monthly starter plan. Leadership learns about big losses the same day rather than at quarter end.
Customer success knows who to talk to
The message names the customer and links to their record, so the account owner can pull up their history and conversations immediately without searching through Stripe. They can open the customer record and start the conversation with context already in hand.
Patterns appear in the channel itself
Three cancellations in one afternoon after a deployment or price change is a signal you can see by scrolling Slack. The feed acts as an early warning for product or billing problems.
Refund and access cleanup happens on time
Knowing a subscription ended promptly lets you remove seats, close accounts or handle pro-rata refunds before the customer has to ask for it, which keeps goodwill intact. Handling the offboarding quickly also shows customers you take their account seriously.
How it works
What happens, step by step
The moment a subscription is cancelled in Stripe, ClickRuntime is told about it.
It looks up the customer's name and email.
A message with the customer and the plan they cancelled is posted to your Slack channel.
Before it runs live
- Connect Stripe
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Stripe steps into one automation
Under the hood
The code that runs this automation
import stripe
from clickruntime import on_event, credentials, notify, verify
@on_event
def handle(event):
if not verify.stripe(event.body, event.header("Stripe-Signature"), credentials.secret("STRIPE_WEBHOOK_SECRET")):
return {"ignored": "bad signature"}
if event.json["type"] != "customer.subscription.deleted":
return {"ignored": event.json["type"]}
sub = event.json["data"]["object"]
stripe.api_key = credentials.secret("STRIPE_API_KEY")
customer = stripe.Customer.retrieve(sub["customer"])
price = sub["items"]["data"][0]["price"]
plan = price.get("nickname") or stripe.Product.retrieve(price["product"]).name
notify.slack(f"Subscription cancelled: {customer.name or 'no name'} ({customer.email}) · {plan}", channel="#revenue")
return {"customer": sub["customer"]}FAQ
Common questions
Does it fire when a customer only schedules a cancellation at period end?
Will trial users who never paid trigger an alert?
Which Slack channel does it post to, and can it tag someone?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get alerted when a payment fails
Each failed charge or invoice payment shows up in Slack with the customer, amount and reason.
See how it worksGet a message for every new sale
Each successful payment reaches you with the customer, amount and what they bought.
See how it worksNever miss a dispute deadline
You hear about each new dispute with its evidence due date, and get a reminder 3 days before it's due.
See how it worksKeep exploring
Set up “Hear when a customer cancels” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.