Daily

Compare yesterday's signups with last week

Every morning you get yesterday's signup count next to the same day last week.

Runs: Daily
Apps: Auth0
AI: Not needed
Access: read:users, read:stats

Send this to your assistant

Create a ClickRuntime automation: every day at 9am, email me how many users signed up in Auth0 yesterday and how that compares to the same day last week.

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

For a SaaS startup, yesterday's signups are the quickest signal of whether marketing worked. The number lives in Auth0, in the user list, and nobody opens that screen for numbers because the product analytics tool is lagging and the user list has no counter. A launch happens on Tuesday, signups double, and nobody notices until the following week. Equally, a broken signup form on Friday goes unnoticed until Monday.

Each morning, ClickRuntime queries Auth0 for users created in yesterday's date range, counts them, compares the total with the same day a week earlier and emails you both numbers. You start the day knowing whether signups are up, down or flat compared with the usual pattern.

It suits small product teams that do not yet have a full analytics setup but want a daily health check.

What you get out of it

Broken signup flows are caught the next morning
A day with zero signups, when the usual is thirty, points straight to a problem with the form or the identity provider. You find out in hours, not at the end of the weekend.
Launch results are seen immediately
When a post or campaign goes out, the next morning's email shows the effect. Marketing can learn which channels and messages work while the details are fresh. Normal dips do not trigger worry, while real ones stand out.
Same-weekday comparison avoids false alarms
Comparing with last week's same day respects weekly patterns, since weekends are naturally quieter. You are not worried by normal dips and you do notice real ones. You learn quickly which channels and messages produce users.
Growth conversations use real numbers
A founder can say signups rose from twenty to thirty-five a day since the pricing change. Claims are backed by a record in your inbox. Statements about growth are backed by a record.
No new tool or dashboard to maintain
The numbers come from the user records Auth0 already holds. You do not need to wire up an analytics product to get a daily count. The count comes straight from your own user records.

How it works

What happens, step by step

Every morning, ClickRuntime counts the Auth0 users created yesterday.
It counts the same day last week too.
You get an email with both counts and the percentage change.

Before it runs live

Connect Auth0

What you get

RunsDaily

Compare yesterday's signups with last weektoday, 9:00Succeeded

Email · 64 Auth0 sign-ups yesterday2026-10-18: 64 sign-ups 2026-10-11: 51 sign-ups Change: +25%

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 Auth0 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.

daily_signups_report.pyexample

from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify

DOMAIN = "northwind.us.auth0.com"

def auth0(path, **params):
    resp = http.get(f"https://{DOMAIN}/api/v2/{path}", params=params,
                    headers={"Authorization": f"Bearer {credentials.secret('AUTH0_MGMT_TOKEN')}"})
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    y, wk = date.today() - timedelta(days=1), date.today() - timedelta(days=8)
    stats = auth0("stats/daily", **{"from": wk.strftime("%Y%m%d"), "to": y.strftime("%Y%m%d")})
    by_day = {s["date"][:10]: s["signups"] for s in stats}
    now, before = by_day.get(str(y), 0), by_day.get(str(wk), 0)
    change = f"{(now - before) / before:+.0%}" if before else "n/a"
    notify.email_me(f"{now} Auth0 sign-ups yesterday", f"{y}: {now} sign-ups\n{wk}: {before} sign-ups\nChange: {change}")
    return {"yesterday": now, "last_week": before}

FAQ

Common questions

Does it count only new signups or also social logins?

It counts every user created in Auth0 within the date range, including social and enterprise connections, since each creates a user record. If you want to separate them, the identity provider field can be used to split the count by connection.

Which timezone defines yesterday?

The date range follows the timezone configured for the flow, which is normally yours. Setting it to match your business hours means a signup at 11 pm local time is counted on the right day, not pushed into the next day's total.

Can it exclude test or internal accounts?

Yes. Accounts can be filtered by email domain or by a metadata flag, so addresses from your own company or from test tenants are skipped. That keeps the number a fair reflection of real customers, which matters when you compare week over week.

What permissions does it need?

read:users, read:stats. 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 (daily). 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.

Every 5 minutes