Collects as they arrive, acts daily
Email a weekly count of new and cancelled subscriptions
Each Monday you see how many subscriptions you gained and lost the week before.
- Runs
- Collects as they arrive, acts daily
- Apps
- Recurly
- AI
- Not needed
- Access
- private API key
Send this to your assistant
Create a ClickRuntime automation: count new and cancelled Recurly subscriptions as they happen, and every Monday at 8am email me last week's totals for each.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
For a subscription business on Recurly, the weekly question is simple: did we gain or lose customers? Finding the answer means filtering subscription lists by date in the admin, counting by hand and then repeating the exercise next week. It rarely gets done consistently, so slow declines go unnoticed until they show up in the quarterly numbers.
As Recurly reports new subscriptions and cancellations through the week, ClickRuntime keeps a count of each. Once a week it emails you the totals and the net change. The window is the same each time, so every digest sits next to the last and trends are visible immediately.
Operators who want a steady read on customer growth without logging in to billing, such as COOs and heads of customer success, will use it most.
What you get out of it
Growth or decline is clear every Monday
The email states how many subscriptions started and how many ended. That is the single most useful number in a recurring revenue business, delivered without any digging. You can plan the week around it.
Slow declines are caught
A loss of two or three customers more than you gain each week barely registers daily. Over a month, it is a real problem, and the digest shows the pattern early. Spotting it in the second week is much cheaper than in the fifth.
Weekly counts replace manual tallies
Counting subscriptions in a list is tedious and error-prone. Counters kept as events arrive are accurate, and they free whoever used to do it for work that needs judgment. The time saved adds up across a year of weeks.
Leadership gets a consistent update
Sending the same figures to executives every week builds a shared language about customer growth. They stop asking for ad hoc numbers because the answer already arrived. Everyone then works from the same figures.
You can link changes to actions
If cancellations jumped the week after a price increase, the digest records it. Linking numbers to decisions is how a team learns what works in pricing and product. Over a year, those links become a record of what moved the numbers.
How it works
What happens, step by step
Throughout the week, each time Recurly reports a new or cancelled subscription, ClickRuntime adds it to a running count.
Once a week, you get an email with the number of new subscriptions, the number cancelled and the net change.
The counts are then reset to zero for the next week.
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, on_trigger, state, notify
@on_event
def count(event):
body = event.json
if body.get("object_type") != "subscription" or body.get("event_type") not in ("created", "canceled"):
return {"counted": False}
counts = state.get("counts") or {"created": 0, "canceled": 0}
counts[body["event_type"]] += 1
state.set("counts", counts)
return {"counted": body["event_type"]}
@on_trigger
def weekly(event):
counts = state.get("counts") or {"created": 0, "canceled": 0}
net = counts["created"] - counts["canceled"]
notify.email_me(f"Recurly last week: {counts['created']} new, {counts['canceled']} cancelled",
f"New subscriptions: {counts['created']}\nCancelled: {counts['canceled']}\nNet: {net:+d}")
state.set("counts", {"created": 0, "canceled": 0})
return countsFAQ
Common questions
How does the digest differ from the Recurly dashboard?
What is counted as a cancellation?
Can I get a breakdown by plan?
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 worksGet 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.
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 worksKeep exploring
Set up “Email a weekly count of new and cancelled subscriptions” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
