Collects as they arrive, acts daily
Get a weekly count of subscription changes
Every Monday you get last week's new, cancelled, paused and skipped subscriptions in one email.
- Runs
- Collects as they arrive, acts daily
- Apps
- Recharge
- AI
- Not needed
- Access
- Subscriptions read
Send this to your assistant
Create a ClickRuntime automation: every Monday at 9am, email me how many Recharge subscriptions were started, cancelled, paused and skipped last week.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A subscription brand lives and dies by its net growth, meaning new subscribers minus cancellations, but Recharge spreads those numbers across several screens and reports. Founders check the figures when they remember, and a week where cancellations outnumbered new customers can pass unnoticed while attention is on ads, inventory and shipping.
As new subscriptions and cancellations arrive through the week, ClickRuntime adds them to running counters. Once a week, it emails you the totals: how many people started, how many left and the net change. The numbers cover the same seven-day window each time, so they can be compared directly from week to week without any adjusting for different date ranges.
It is designed for brands that want one reliable number for growth without opening reports or exporting data each week.
What you get out of it
Net growth is a number you actually see
Seeing plus 42 new and minus 31 cancelled in one line tells you whether the base is growing. That is the question every subscription owner asks, answered without effort. There is no spreadsheet and no filtering involved.
Bad weeks stand out
A week with more cancellations than sign-ups is a warning. Because the email arrives regardless, you notice even when you have been busy elsewhere, and you can investigate while the cause is recent.
Campaign results are easier to judge
Launching an ad push or a discount shows up as a jump in new subscribers. Comparing consecutive weeks tells you whether the extra spend brought lasting subscribers or a short spike.
Counts come from the events themselves
Because each new subscription and cancellation is counted as it happens, the totals do not depend on someone exporting a report. That avoids date range errors and double counting. That also removes the common mistake of counting the same customer twice.
A shared pulse for partners and investors
Forwarding the same simple summary every week keeps others informed. It sets expectations and builds trust, since they hear about dips from you rather than discovering them later. Steady updates build confidence more than occasional good news.
How it works
What happens, step by step
Each time a Recharge subscription is started, cancelled, paused or skipped, ClickRuntime adds it to a count for the week.
Every Monday at 9am it sends you one email with the four totals.
The counts are then reset for the new week.
Before it runs live
- Connect Recharge
- 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 Recharge steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, on_trigger, state, notify
TOPICS = {"subscription/created": "started", "subscription/cancelled": "cancelled",
"subscription/paused": "paused", "subscription/skipped": "skipped"}
@on_event
def handle(event):
kind = TOPICS.get(event.header("X-Recharge-Topic"))
if kind:
counts = state.get("week") or {}
counts[kind] = counts.get(kind, 0) + 1
state.set("week", counts)
return {"counted": kind}
@on_trigger
def run(event): # Monday 9am
counts = state.get("week") or {}
notify.email_me("Recharge subscriptions last week",
"\n".join(f"{k.title()}: {counts.get(k, 0)}" for k in TOPICS.values()))
state.delete("week")
return countsFAQ
Common questions
How are the weekly counters kept?
What happens if the week has no activity?
Does it count reactivated subscriptions as new?
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
Find out the main reasons customers cancel
Once a month you get the cancellation reasons grouped into a few themes, with how often each came up.
See how it worksGet an email when a subscription payment fails
Each failed charge, and each one that runs out of retries, reaches you with the customer and amount so you can follow up.
See how it worksPost each cancellation and its reason to Slack
Your team sees who cancelled, which product they had and the reason they gave, as it happens.
See how it worksKeep exploring
Set up “Get a weekly count of subscription changes” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
