Automate Clerk

Know who is joining your product as it happens. Clerk sends each new user and each newly created organization to ClickRuntime the moment they appear, and every Monday you get the past week's signup total and trend. Ask your AI assistant for what you need, check what it will set up, and it stays on without you.

Add to ChatGPT Add to Claude

Works inChatGPT Claude Claude Code Cursor Codex VS Code Gemini CLI Zed opencode Any MCP client

Try asking

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.

Ideas

What you can automate in Clerk

Instant word on new users and new teams, plus a weekly read on how signups are trending. These are ready-made starting points. Anything else you can describe works too.

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.

See how it works

The moment it happens

Get an email when a team creates an organization

You hear about each new organization as soon as it's created, so you can reach out to the team.

See how it works

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.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Clerk, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Clerk automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Clerk should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

When a new user signs up through Clerk, have AI check whether the email domain looks like a company and send me only the business signups.

When a user signs up in Clerk, post their name, email and sign-in method to our #signups Slack channel.

When a Clerk user signs up, create a HubSpot contact, add them to my Google Sheets user list, and send a welcome email through Gmail.

Beyond chat

Have Clerk work when you're not in the chat

Connecting Clerk to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Instant
Post each new Clerk user to Slack
The moment it happens
On a schedule
Get last week's signup total every Monday
Weekly
Instant
Get an email when a team creates an organization
The moment it happens

Setup

Connect Clerk

Clerk connects with the Backend API secret key of your instance. Development and production each have their own key.

Clerk

Identity / Auth for developers

In the Clerk Dashboard, select the instance you want to automate, development or production.
Go to Configure → Developers → API Keys.
Copy the Secret key. It starts with sk_live_ for production or sk_test_ for development.
In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret.

Good to know

Clerk limits that affect automations

The secret key has full backend access to the instance, so keep it out of shared documents.
Development and production instances are separate. A sk_test_ key won't see production users.
New user and new organization alerts rely on a Clerk webhook, which you add in the Clerk Dashboard using the link ClickRuntime gives you.
Rate limits apply per instance, so very large counts may take a little longer to read.

FAQ

Questions about automating Clerk

What can ClickRuntime see in Clerk?

The secret key gives backend access to the instance's users and organizations. These automations read new users and organizations, and count signups.

Are new-user alerts instant?

Yes. Clerk sends a webhook when a user or organization is created, so the alert goes out straight away instead of on a schedule.

Which key should I use, test or live?

Use the `sk_live_` key to watch real signups. The `sk_test_` key only sees your development instance.

Do I need AI?

No, these alerts and reports run without it. If you want AI in a later automation, it comes with every ClickRuntime plan, and you don't need your own key.

Is this a Clerk connector for ChatGPT or Claude?

Not for chatting with Clerk data. A chat connector lets your assistant read and change Clerk while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Clerk event.

Keep exploring

Tell your assistant what Clerk should do

Free plan. No credit card.