The moment it happens

Post each new Clerk user to Slack

The moment someone signs up, their name and email show up in your channel.

Runs: The moment it happens
Apps: Clerk
AI: Not needed
Access: secret key (webhook set in dashboard)

Send this to your assistant

Create a ClickRuntime automation: when a new user is created in Clerk, post their name and email to #new-users 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

Product teams like to say they watch signups, but in practice they check a dashboard a couple of times a week. In between, a promising customer registers, finds nothing guiding them, and never comes back. Nobody on the team even knew they had arrived, so nobody could say hello.

When Clerk reports a new user, this posts their name and email to the Slack channel you choose, the moment it happens. The channel becomes a live feed of who is joining, visible to everyone from support to the founder.

Small teams use it to keep a human feel on early growth, and larger ones use it to route interesting signups to sales quickly. The post is created from the Clerk event itself, so it reflects the real account that was created and does not depend on anyone remembering to announce it.

What you get out of it

Welcome people while they are still there
A signup is highest in intent right after registering. Seeing the name in Slack lets someone send a personal hello or offer a demo before that curiosity fades. A quick hello often turns a signup into an active user, particularly when the sender mentions something specific about the product.
Let sales spot valuable signups
A corporate email domain jumps out in a stream of names. Sales can pick those up for outreach within minutes without writing a query against the user table. That lead gets handled before it disappears into a long list, because the corporate address is visible the instant it arrives.
Give the whole team shared visibility
Support and engineering see who is joining. When a new user reports a bug five minutes later, the team already recognizes their name and can respond with context. It also shortens the time to a useful reply, since support recognizes the name from the channel before the first message arrives.
Detect signup problems immediately
If the feed suddenly goes silent after a deploy, or fills with suspicious addresses, you notice right away. Broken registration or bot attacks are found in minutes rather than at the weekly review.
Build a lightweight customer log
The channel history is a dated record of who signed up and when. It is useful for reconstructing a growth spike after a launch or press mention. It also doubles as a quick way to check marketing results, because a campaign shows up as a burst of new names.

How it works

What happens, step by step

When someone signs up through Clerk, Clerk tells ClickRuntime straight away.
Their name and email are posted to your Slack channel.
Each person is posted once, at the moment their account is created.

Before it runs live

Connect Clerk
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Post each new Clerk user to Slackjust nowSucceeded

Slack · #new-usersNew user: Lee Park (lee@acme.example)

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

new_user_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    payload = event.json or {}
    if payload.get("type") != "user.created":
        return {"posted": False}
    u = payload["data"]
    email = next((e["email_address"] for e in u.get("email_addresses", [])
                  if e["id"] == u.get("primary_email_address_id")), "no email")
    name = " ".join(filter(None, [u.get("first_name"), u.get("last_name")])) or "New user"
    notify.slack(f"New user: {name} ({email})", channel="#new-users")
    return {"posted": True}

FAQ

Common questions

Does the message include a phone number or other fields?

It posts the name and email. If you also want the sign-up method, such as Google or email link, or any metadata, ask for it to be added and review the updated message format before approving. Any extra field carried by the event can be added to the post, such as the sign-in method or a verified email flag.

Will test users appear in the channel?

Any user created in the Clerk instance connected to the webhook will appear. Use a separate development instance for testing, or ask for a filter that ignores addresses at your own domain. A staging instance keeps your real channel clean, and each Clerk instance has its own webhook endpoint and signing secret.

Is the Clerk webhook verified?

Yes. Clerk signs its webhooks, and the endpoint checks that signature using a secret stored securely. Posts to Slack only happen for genuine events from your Clerk application. Unsigned requests are rejected before anything is posted, so a stranger who finds the URL cannot fill your channel with fake signups.

What permissions does it need?

secret key (webhook set in dashboard). 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 for each event the app sends.

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