Weekly

Get last week's signup total every Monday

Each Monday you see how many people signed up the previous week and whether it went up or down.

Runs: Weekly
Apps: Clerk
AI: Not needed
Access: secret key

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me how many users signed up in Clerk last week and how that compares to the week before.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Founders and growth leads want one number each week: how many people signed up, and whether that is better or worse than before. Getting it means opening an analytics tool, choosing a date range, copying a figure into a spreadsheet, and remembering last week's value. Most weeks that chore gets skipped, and trends go unseen.

Every week, this counts the Clerk users created in the reporting period, compares the count with the figure it stored from the previous run, and emails you the total and the change. It does the counting and the remembering for you.

It is meant for teams who want a steady growth pulse without building a dashboard, such as pre-launch startups watching waitlist conversion. Because the counts are stored from one week to the next, the email gets more valuable the longer it runs, and the comparison never depends on anyone's memory.

What you get out of it

Track growth without opening a dashboard
The number simply arrives in your inbox. Because you do not have to remember to look, the habit of checking growth survives busy weeks and holidays. It also removes the awkwardness of reconstructing last week's figure from an old spreadsheet or a half-remembered chat message.
See direction, not just totals
A count alone says little. Because the email includes the change from last week, you can tell at a glance whether a campaign moved signups up, down, or nowhere. That context is what turns a bare figure into a decision, such as repeating a campaign that worked or dropping one that did not.
Link signups to what you did
Weekly granularity lines up with launches, newsletters and ad changes. When a number jumps, you can recall exactly what you shipped that week and judge whether it worked. Seeing it quickly prevents a month of lost signups from a form that quietly stopped working after a deploy.
Spot a stalled funnel early
If signups fall 40% with no explanation, that might be a broken form or a tracking change. A weekly alert gets you looking at it within days rather than at quarter end.
Create investor-ready history
Stored week-over-week counts become a simple growth record. When you need numbers for an update, you have a consistent series rather than a reconstruction. Nothing else needs to be maintained for this to keep working, so it keeps running through busy weeks and vacations.

How it works

What happens, step by step

Every Monday, ClickRuntime counts the Clerk users created in the last seven days.
It compares that with the total saved from the week before.
You get an email with both weeks and the percentage change. This week's total is saved for next time.

Before it runs live

Connect Clerk

What you get

RunsWeekly

Get last week's signup total every Mondaytoday, 9:00Succeeded

Email · 318 Clerk sign-ups last weekLast 7 days: 318 Week before: 274 Change: +16%

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

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

Run it at a different time, more or less often, or only on weekdays
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 Clerk steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

weekly_signups_report.pyexample

import time
from clickruntime import on_trigger, credentials, http, notify

def count(after_ms, before_ms):
    resp = http.get("https://api.clerk.com/v1/users/count",
                    headers={"Authorization": f"Bearer {credentials.secret('CLERK_SECRET_KEY')}"},
                    params={"created_at_after": after_ms, "created_at_before": before_ms})
    resp.raise_for_status()
    return resp.json()["total_count"]

@on_trigger
def run(event):
    week = 7 * 86400 * 1000
    now = int(time.time() * 1000)
    last, prev = count(now - week, now), count(now - 2 * week, now - week)
    change = f"{(last - prev) / prev:+.0%}" if prev else "n/a"
    notify.email_me(f"{last} Clerk sign-ups last week", f"Last 7 days: {last}\nWeek before: {prev}\nChange: {change}")
    return {"last_week": last, "week_before": prev}

FAQ

Common questions

How are signups counted?

It counts Clerk users whose creation date falls inside the reporting week. Users who sign in again later are not counted twice, and deleted users are not part of the Clerk user list. The count follows Clerk's own creation date for each user, so a profile edited later is not counted again.

What happens on the very first run?

There is no stored figure from before, so the first email shows the current count without a comparison. From the second week onward, the email includes the change against the previous number. The saved figure is the base for every later week, and each new run replaces it with the latest count.

Can I count only users from a specific source?

If Clerk stores the information in user metadata, a filter can be added to count only those users. Describe it to your AI assistant and approve the new step before it takes effect. The filter would be applied before the total is calculated, so the email only ever reports the segment you care about.

What permissions does it need?

secret key. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens