Daily

See yesterday's new sign-ups each morning

A private email lists the accounts created in the last 24 hours, with how each person signed in and the running total.

Runs: Daily
Apps: Firebase
AI: Not needed
Access: firebase or cloud-platform scope; Firebase Authentication Viewer role

Send this to your assistant

Create a ClickRuntime automation: every morning at 8am, email me the Firebase Auth users created in the last 24 hours with their email and sign-in provider, plus how the count compares with the day 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

When a product starts to get users, the founder wants to know who they are: a company they recognize, a competitor, someone who might be a good customer to call. Firebase Authentication shows the list of accounts, but only by opening the console and sorting by created date, and nobody does this every day. Interesting sign-ups pass by for weeks before anyone notices, and the best moment to say hello, right after someone tries the product, is lost.

Every morning, ClickRuntime queries your accounts sorted by created date, keeps those created in the last 24 hours, and emails you the list with a total. It also stores the daily count so the email can show how the number moves over time.

Founders doing their own sales, and customer success people who like to greet new users personally, tend to like it most.

What you get out of it

Welcome new users personally
A short message to a new user on their first day often gets a reply. Early conversations tell you why they signed up and what they hoped the product would do.
Spot promising accounts
Seeing email domains in a list shows company users among the personal addresses. A sales-minded founder can reach out to the interesting ones before the free trial fades from memory.
Detect spam or fake sign-ups
A burst of accounts from throwaway addresses is visible in a morning list. You can add verification or tighten rules before fake accounts distort your numbers and email reputation. That protects deliverability.
Learn who your audience is
Reading names and domains over a few weeks tells you who actually uses the product. That is far more concrete than analytics, and it shapes your next feature and messaging.
Track growth without analytics tools
The stored count builds a daily history you can chart. Early-stage teams without a data stack get a basic growth record with no extra tooling. A simple chart is easy to build later.

How it works

What happens, step by step

Every morning ClickRuntime looks at the Firebase accounts created in the last 24 hours.
It lists each new user with how they signed in, such as Google or email.
It compares the count with the day before.
You get a private email with the list and the count.

Before it runs live

Connect Firebase

What you get

RunsDaily

See yesterday's new sign-ups each morningtoday, 9:00Succeeded

Email · New sign-ups18 new sign-ups (+5 vs the day before) ops@northwind.example via google.com

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

get_a_daily_list_of_new_sign_ups.pyexample

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

PROJECT = "acme-prod"

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.connection('google', 'work')}"}
    body = {"returnUserInfo": True, "limit": 500, "sortBy": "CREATED_AT", "order": "DESC"}
    users = http.post(f"https://identitytoolkit.googleapis.com/v1/projects/{PROJECT}/accounts:query",
                      headers=headers, json=body).json().get("userInfo", [])
    cutoff = (time.time() - 86400) * 1000
    new = [u for u in users if int(u["createdAt"]) >= cutoff]
    before = state.get("last_count")
    lines = [f"{u.get('email', '(no email)')} via {(u.get('providerUserInfo') or [{}])[0].get('providerId', 'anonymous')}" for u in new]
    trend = f" ({len(new) - before:+d} vs the day before)" if before is not None else ""
    notify.email_me(f"{len(new)} new sign-ups{trend}", "\n".join(lines) or "No sign-ups.")
    state.set("last_count", len(new))
    return {"new": len(new)}

FAQ

Common questions

Does it show names and emails of users?

It lists the fields your account records contain, usually email and display name, plus the creation time. If you prefer not to put emails in a message, the list can include only domains or user IDs. Fewer fields keep the email short.

What counts as the last 24 hours?

The run takes accounts whose created date falls within the 24 hours before it runs, using timestamps from Firebase Authentication. Running at the same time each day gives non-overlapping windows with no duplicates. Scheduling at a fixed hour avoids gaps.

Do I need the Firebase Admin credentials?

Reading the account list needs a service account with permission to view Firebase Authentication users. The key is stored as a secret in ClickRuntime and used only for this lookup, never printed in the email.

What permissions does it need?

firebase or cloud-platform scope; Firebase Authentication Viewer role. 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.

Daily