The moment it happens
Get a Slack message when a Recurly subscription is cancelled
You hear about cancellations as they happen, so key accounts get a call before they leave.
- Runs
- The moment it happens
- Apps
- Recurly
- AI
- Not needed
- Access
- private API key
Send this to your assistant
Create a ClickRuntime automation: whenever a Recurly subscription is cancelled, post the account name, plan and cancellation date to #account-management in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
On a SaaS or membership product billed through Recurly, most cancellations are small, but a few are accounts that matter: an annual enterprise plan, a customer who came through a major partner, or someone who has been paying for years. If one of those cancels on a Friday, nobody on the account team knows until the renewal forecast is reviewed.
When an account cancels a subscription in Recurly, ClickRuntime receives the notification and posts it in Slack straight away. The message shows the account name, the plan and the cancellation details so the owner of the relationship can react. It runs on the event itself, so the post appears within moments.
It is most useful for customer success teams who manage a handful of valuable accounts and need to know the same day if one is leaving.
What you get out of it
Key accounts get a same-day call
A call on the day of cancellation can find out the reason, correct a misunderstanding or offer a plan change. A week later the customer has often already moved to a competitor.
Renewal forecasts stay accurate
When a cancellation is seen immediately, the forecast reflects it. Leaders are not surprised at quarter end by revenue that quietly disappeared a month earlier. Planning decisions then rest on real numbers.
Plan context is in the message
Knowing whether the account was on a starter or an enterprise plan changes the response. The alert carries the plan, so you can prioritize at a glance. An enterprise customer leaving needs a different response than a trial user.
Account owners are never blindsided
Customer success managers often learn about churn from finance. A direct alert reverses that, and the person who knows the customer best is told first. That changes the conversation from damage control to a real attempt at keeping the account.
Learning from losses starts early
Each lost account is a chance to understand what failed. Capturing the moment in a shared channel starts a conversation while details are fresh, instead of leaving it to a quarterly post-mortem. Teams that review every loss tend to find the same fixable causes repeatedly.
How it works
What happens, step by step
When a Recurly subscription is cancelled, Recurly tells ClickRuntime straight away.
ClickRuntime reads the account, the plan, the cancellation date and when access ends.
A message goes to your #account-management Slack channel with the customer, the plan, the date it was cancelled and when access ends.
Before it runs live
- Connect Recurly
- 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 Recurly steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, notify
API = "https://v3.recurly.com"
def recurly(path):
resp = http.get(f"{API}{path}", auth=(credentials.secret("RECURLY_API_KEY"), ""),
headers={"Accept": "application/vnd.recurly.v2021-02-25+json"})
resp.raise_for_status()
return resp.json()
@on_event
def handle(event):
body = event.json
if (body.get("object_type"), body.get("event_type")) != ("subscription", "canceled"):
return {"posted": False}
sub = recurly(f"/subscriptions/uuid-{body['uuid']}")
account = sub["account"]
name = account.get("company") or f"{account.get('first_name', '')} {account.get('last_name', '')}".strip()
notify.slack(f"{name} cancelled *{sub['plan']['name']}* on {sub['canceled_at'][:10]}; "
f"access ends {(sub.get('current_period_ends_at') or '')[:10]}", channel="#account-management")
return {"subscription": sub["id"]}FAQ
Common questions
Does the alert cover only key accounts or every cancellation?
Is a cancellation the same as an expiration in Recurly?
Can I get notified for downgrades too?
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
Track failed Recurly renewals and dunning in Slack
Each failed renewal or dunning step appears in your channel with the account, amount and plan.
See how it worksPost new Recurly subscriptions to Slack
Every new subscription shows up with the account, plan and price as soon as it starts.
See how it worksEmail a weekly count of new and cancelled subscriptions
Each Monday you see how many subscriptions you gained and lost the week before.
See how it worksKeep exploring
Set up “Get a Slack message when a Recurly subscription is cancelled” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
