Every 5 minutes

Ping your team when someone signs up

Each new Auth0 user is posted to your channel with their email a few minutes after signing up.

Runs: Every 5 minutes
Apps: Auth0
AI: Not needed
Access: read:users

Send this to your assistant

Create a ClickRuntime automation: every 5 minutes, check Auth0 for users created since the last check and post each new user's email and sign-up method to #signups in Slack.

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 an early-stage product, each new user matters, and many founders like to greet the first few hundred personally. The trouble is knowing they arrived. Auth0 holds the user list, but there is no built-in message when someone signs up, so the founder checks the dashboard when they remember. A promising user from a target company signs up on Tuesday afternoon and receives a welcome email only on Thursday, if at all.

Every five minutes, ClickRuntime searches Auth0 for users created since its last check, posts the email addresses of any new ones to Slack and saves the time for the next run. Your team sees signups within minutes and can follow up while the person is still exploring the product.

It is useful for small teams that do onboarding by hand and want to see who is arriving in real time.

What you get out of it

Personal welcomes happen while users are active
A short human message sent within minutes, while someone is still clicking around, gets more replies than one sent two days later. First impressions are formed early. First impressions form during the first visit.
Target customers are spotted immediately
Seeing a company domain you have been trying to reach appear in the channel lets sales act that day. Inbound interest from a hard-to-reach account is rarely repeated. Inbound interest from hard-to-reach accounts rarely repeats.
Spam and fake signups are visible
A run of signups from odd addresses is obvious in the channel. You can block bots before they pollute your metrics or send unwanted mail. Blocking early protects your metrics and your mailing reputation.
The team shares a moment of progress
Watching signups arrive in Slack is motivating, especially at launch. Seeing real people join keeps everyone connected to customers, not only to code. Customer contact keeps everyone focused on real people.
Support is ready for new users
If a new user hits problems at signup, a teammate who saw them arrive can offer help right away. Quick help turns confusion into retention. Quick help turns confusion into retention for new accounts.

How it works

What happens, step by step

Every 5 minutes, ClickRuntime checks Auth0 for users created since its last check.
Each new sign-up is posted to your Slack channel with their email and how they signed up, such as Google.
It remembers the last check, so each person is posted once.

Before it runs live

Connect Auth0

What you get

RunsEvery 5 minutes

Ping your team when someone signs uptoday, 9:00Succeeded

Slack · #signupsNew sign-up: lee@acme.example via google-oauth2

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

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

new_signup_alert.pyexample

from datetime import datetime, timezone
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched

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):
    since = state.get("since") or datetime.now(timezone.utc).isoformat()[:23]
    users = auth0("users", q=f"created_at:{{{since} TO *]", search_engine="v3", sort="created_at:1", per_page=100)
    report_fetched(len(users))
    if not users:
        return {"summary": "Nothing new"}
    for u in users:
        notify.slack(f"New sign-up: {u.get('email')} via {u['identities'][0]['provider']}", channel="#signups")
    state.set("since", users[-1]["created_at"])
    return {"new": len(users)}

FAQ

Common questions

How does it avoid posting the same user twice?

Each run remembers the time of the latest user it saw, and the next run asks Auth0 only for users created after that time. This keeps a user from appearing again, even if the flow runs many times a day.

Is it a problem to share email addresses in Slack?

Email addresses are personal data, so post them only in a channel that your team already uses for customer information. If you prefer, the message can show only the domain or a masked address, which still helps spot target companies.

Can I get a message only for business email domains?

Yes. The flow can skip free providers like Gmail or Outlook and post only addresses from company domains. This is a common change for B2B products, since it keeps the channel focused on the signups that sales would act on.

What permissions does it need?

read:users. 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 checks. Checks that find nothing new 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 15 minutes