Collects as they arrive, acts daily
Get your weekly subscriber gains and losses
Every Monday you see how many readers joined, how many left, and your current total.
- Runs
- Collects as they arrive, acts daily
- Apps
- beehiiv
- AI
- Not needed
- Access
- API key
Send this to your assistant
Create a ClickRuntime automation: every Monday at 8am, email me how many beehiiv subscribers I gained and lost last week and my total subscriber count.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Growth for a newsletter is not a single number. New subscribers, unsubscribes and the net total each tell a different story. A week with 400 new subscribers and 350 unsubscribes looks fine on a total, but means something is wrong with retention. The publisher who only sees the total misses that churn is eating the gains, and decisions about promotion budgets rest on an incomplete picture.
During the week, ClickRuntime counts subscription and unsubscription events in weekly counters. On Monday it fetches the publication's current stats from beehiiv and emails you new subscribers, unsubscribes and the total. The three numbers appear together, so growth is judged properly.
Independent publishers and small media teams who set weekly targets will use it as a simple scoreboard. It also gives a sponsor a simple view of the audience.
What you get out of it
Churn cannot hide behind growth
Seeing unsubscribes beside new subscribers shows whether you are really growing. A weak retention problem becomes visible while it can still be fixed. A retention problem becomes visible while it can still be fixed cheaply and quickly.
Promotion spending can be judged
If you paid for a promotion, the week's numbers show what it delivered. Without them, you may spend more on something that brings readers who leave quickly. Spending decisions then rest on what each promotion actually delivered, not on hope.
Targets feel concrete
A weekly net number is easy to set goals against. A team can aim for a specific increase and see whether they reached it, which is more motivating than a vague aim to grow.
Trends appear across weeks
Looking at several Monday emails shows direction, such as growing slowly or flattening. You can respond to a trend before it becomes a problem. You can respond to a flattening trend long before it turns into a real problem.
Reporting to partners is easy
A sponsor, a co-founder or an investor can be sent the same numbers. Regular reporting builds trust, and you do not have to build a report each time. Your reports to sponsors stay consistent without any extra spreadsheet work.
How it works
What happens, step by step
Each time someone subscribes to or leaves your beehiiv newsletter, ClickRuntime adds it to that week's tally.
Every Monday it reads last week's numbers of readers gained and lost.
It fetches your current total of active subscribers from beehiiv.
You get one email with gained, lost, the net change and your total.
Before it runs live
- Connect beehiiv
- 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 beehiiv steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, on_trigger, credentials, http, state, notify
PUB_ID = "pub_00000000-0000-0000-0000-000000000000"
@on_event
def count(event):
kind = event.json.get("event_type")
if kind in ("subscription.created", "subscription.deleted"):
state.increment_metric(kind, ttl_days=60, bucket="week")
return {"counted": kind}
@on_trigger
def report(event):
def last_week(key):
points = state.query_metric(key, bucket="week")
return points[-2]["value"] if len(points) >= 2 else 0
gained, lost = last_week("subscription.created"), last_week("subscription.deleted")
pub = http.get(f"https://api.beehiiv.com/v2/publications/{PUB_ID}", params={"expand[]": "stats"},
headers={"Authorization": f"Bearer {credentials.secret('BEEHIIV_API_KEY')}"}).json()["data"]
total = pub["stats"]["active_subscriptions"]
notify.email_me("beehiiv growth last week", f"Gained: {gained}\nLost: {lost}\nNet: {gained - lost:+}\nTotal: {total:,}")
return {"gained": gained, "lost": lost, "total": total}FAQ
Common questions
Where do the new and unsubscribed counts come from?
What if I turn it on in the middle of a week?
Does it separate free and premium subscribers?
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 a recap a day after each issue
24 hours after a post goes out, you get its open rate, click rate and the links readers clicked most.
See how it worksPost new beehiiv subscribers to Slack
Each new reader appears in Slack with their email and where they signed up from.
See how it worksShare reader survey answers in Slack
When a reader answers one of your surveys, the response is posted for the team to read.
See how it worksKeep exploring
Set up “Get your weekly subscriber gains and losses” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
