How to Set Up Clerk Webhook Notifications with Webhookify

Published Feb 21 202610 min read
Clerk webhook setup with Webhookify

Clerk is the modern authentication and user management platform that developers love for building secure, production-ready signup and login experiences. Every time a user signs up, updates their profile, deletes their account, starts a session, or joins an organization, Clerk fires a webhook event. For SaaS founders and development teams, monitoring these authentication events is critical -- a sudden spike in new signups could indicate a successful marketing campaign, while unusual session patterns might signal a security concern. With Webhookify, you can instantly receive human-readable notifications for every Clerk webhook event on Telegram, Discord, Slack, Email, or your mobile device, giving you real-time visibility into your application's user activity.

This guide walks you through connecting Clerk webhooks to Webhookify, from creating your endpoint to receiving your first real-time authentication alert. Whether you are tracking user growth for your SaaS product or monitoring security events across your application, this setup takes less than 15 minutes and requires no additional code in your application.

Why Monitor Clerk Webhooks with Webhookify?

  • Real-Time Signup Tracking: Know the moment a new user creates an account in your application. Webhookify delivers AI-summarized alerts within seconds, letting founders and growth teams celebrate every new user and track acquisition in real time.

  • Multi-Channel Delivery: Route Clerk authentication alerts wherever your team works. Send new user signups to a Slack channel, session events to a security monitoring Discord channel, and organization changes to Email -- all from a single Webhookify endpoint.

  • Security Monitoring: Track user session creation and termination events in real time. Unusual patterns like many failed sessions or accounts being deleted can be flagged immediately, allowing your team to investigate potential security issues.

  • AI-Powered Summaries: Instead of parsing Clerk's JSON webhook payloads, Webhookify transforms the data into plain-English summaries like "New user john@example.com signed up via Google OAuth. Email verified. User ID: user_abc123."

  • Complete Audit Trail: Every webhook Clerk sends is logged with full headers and payload data. This creates a comprehensive authentication audit trail for compliance, debugging, and user activity analysis.

Prerequisites

  1. A Clerk account with an active application (free to create at clerk.com)
  2. A Webhookify account (sign up free at webhookify.app)
  3. At least one notification channel configured (Telegram, Discord, Slack, Email, or mobile push)
  4. Access to the Clerk Dashboard with permission to manage webhooks

Step-by-Step Setup Guide

1

Create a Webhookify Endpoint

Start by logging into your Webhookify dashboard at webhookify.app. If you do not have an account yet, sign up -- the free tier is all you need to get started.

Once inside the dashboard, click the "Create Endpoint" button. Webhookify will generate a unique webhook URL that looks something like this:

https://hook.webhookify.app/wh/abc123xyz789

Copy this URL and keep it handy. This is the URL you will paste into Clerk's webhook endpoint configuration. Each endpoint has its own event log, so you can create separate endpoints for different Clerk applications or environments (development vs. production).

Give your endpoint a descriptive name like "Clerk Production Auth Events" or "Clerk User Signups" so you can easily identify it later in your dashboard.

2

Configure Your Notification Channel

Before connecting Clerk, make sure you have at least one notification channel set up in Webhookify. Navigate to the Settings or Notifications section in your Webhookify dashboard.

For Telegram: Click "Connect Telegram" and follow the bot authorization flow. You can send notifications to a private chat, a group, or a channel. This is great for founders who want instant signup alerts on their phone.

For Discord: Click "Connect Discord" and authorize the Webhookify bot to post in your selected server and channel. Choose a dedicated channel like #auth-events or #user-signups to keep authentication notifications organized.

For Slack: Click "Connect Slack" and complete the OAuth flow. Select the workspace and channel where you want Clerk alerts to appear. A channel like #user-activity or #auth-alerts works well.

For Email: Enter the email address where you want to receive webhook notifications. You can add multiple addresses to notify your security and growth teams.

For Mobile Push: Download the Webhookify app from the App Store or Google Play. Sign in with your account credentials. Enable push notifications when prompted so you receive instant alerts for every authentication event.

3

Add Your Webhookify URL in Clerk

Log into the Clerk Dashboard and select the application you want to monitor.

  1. Navigate to Webhooks in the left sidebar.
  2. Click "Add Endpoint".
  3. In the "Endpoint URL" field, paste your Webhookify URL:
https://hook.webhookify.app/wh/abc123xyz789

  1. Under "Subscribe to events", select the events you want to monitor. For comprehensive user monitoring, select:

    • user.created
    • user.updated
    • user.deleted
    • session.created
    • session.ended
    • organization.created
    • organization.membership.created

  2. Click "Create" to save the endpoint.

Clerk will display the endpoint along with a Signing Secret. You can note this for reference, but Webhookify handles receiving and logging the webhooks automatically. Clerk uses Svix under the hood for reliable webhook delivery with automatic retries.

4

Configure Event Filters and Alert Preferences

Back in your Webhookify dashboard, click on your Clerk endpoint to fine-tune notification delivery.

The key Clerk events to monitor include:

  • user.created -- A new user signed up for your application
  • user.updated -- A user updated their profile, email, or phone number
  • user.deleted -- A user deleted their account
  • session.created -- A user logged in and a new session was created
  • session.ended -- A user session was terminated (logout or expiration)
  • organization.created -- A new organization was created
  • organization.membership.created -- A user was added to an organization

Configure notification routing based on event priority. For example:

  • Send user.created events to Slack for the growth team to celebrate
  • Route user.deleted events to Email so the team can analyze churn
  • Send session.created and session.ended events to a lower-priority Discord channel for security monitoring
5

Test Your Configuration

Clerk provides a built-in webhook testing tool. In the Clerk Dashboard, go to Webhooks, click on your endpoint, and use the "Send Test Event" feature.

Select an event type like user.created and send the test. Within seconds, you should receive a notification on your configured channels.

You can also test with real events by creating a new user in your application's development environment. Sign up using the test application's frontend, and the user.created webhook will fire immediately.

Check your Webhookify dashboard to see the test event logged with its full payload. Clerk webhooks include detailed user information such as email addresses, authentication methods, creation timestamps, and metadata.

If you do not receive a notification, verify that:

  • The endpoint URL is correctly saved in the Clerk Dashboard
  • The desired events are selected for the endpoint
  • Your Webhookify notification channel is connected and active

Clerk Webhook Events You Can Monitor

Clerk EventDescription
user.createdTriggered when user created occurs
user.updatedTriggered when user updated occurs
user.deletedTriggered when user deleted occurs
session.createdTriggered when session created occurs
session.endedTriggered when session ended occurs
session.removedTriggered when session removed occurs
organization.createdTriggered when organization created occurs
organization.updatedTriggered when organization updated occurs
organization.deletedTriggered when organization deleted occurs
organization.membership.createdTriggered when organization membership created occurs
organization.membership.updatedTriggered when organization membership updated occurs
organization.membership.deletedTriggered when organization membership deleted occurs
email.createdTriggered when email created occurs
sms.createdTriggered when sms created occurs

Real-World Use Cases

  • SaaS Signup Tracking: A startup founder receives a Telegram notification every time a new user signs up for their application. The AI summary includes the user's email, authentication method (Google OAuth, email/password, etc.), and whether email verification is complete. This gives real-time visibility into user acquisition without checking analytics dashboards.

  • Security Auditing: A development team routes session events to a dedicated Discord channel. They monitor for unusual patterns like multiple session creations from different locations in a short time period, which could indicate credential stuffing or account compromise. The Webhookify event log provides a complete audit trail.

  • Organization Growth Monitoring: A B2B SaaS product tracks organization.created and organization.membership.created events via Slack. When a new company signs up or adds team members, the sales team is notified and can proactively reach out to offer onboarding support.

  • Churn Analysis: The customer success team monitors user.deleted events via Email. Each notification includes the user's information, allowing the team to send win-back campaigns or analyze patterns in account deletions to improve the product.

Example Notification

Here is what a typical Webhookify notification looks like when a new user signs up via Clerk:

New Webhook Event Received

Source: Clerk
Event: user.created
Endpoint: Clerk Production Auth Events

AI Summary:
New user signup! sarah@example.com created an account
using Google OAuth. Email is verified. User ID:
user_2nKx8fQPmBwR5j. First name: Sarah, Last name:
Chen. Account created in the production environment.

Timestamp: 2026-02-21T08:15:22Z

View full payload in Webhookify Dashboard

Troubleshooting

  1. Webhook not arriving in Webhookify: Verify the endpoint URL in the Clerk Dashboard exactly matches your Webhookify URL. Check that the endpoint status shows as "Active." Clerk uses Svix for delivery, which includes automatic retries, so transient failures are usually resolved automatically.

  2. Missing events for specific actions: Ensure the specific event types are selected in your Clerk webhook endpoint configuration. If you only selected user.created but want session events too, you need to edit the endpoint and add session.created and session.ended to the subscription.

  3. Notification not received but webhook is logged: If the event appears in your Webhookify dashboard but no notification was sent, check your notification channel configuration. The channel may be disconnected or the notification preferences may be filtering out the event type.

  4. Webhook signature verification errors in logs: Clerk signs webhooks using Svix. While Webhookify receives and logs these webhooks regardless of signature status, if you see signature-related warnings, ensure your endpoint URL does not have any redirects that might alter the request headers.

  5. Development vs. production events: Clerk maintains separate webhook configurations for each instance (development, staging, production). Make sure you are configuring webhooks in the correct instance. Create separate Webhookify endpoints for each environment to avoid mixing development and production events.

Create a dedicated Webhookify endpoint for your Clerk production environment and a separate one for development. Name them clearly (e.g., "Clerk Production" and "Clerk Development") so you can instantly distinguish between real user signups and test events. This prevents false excitement from development-environment signups.

Track Every User Signup in Real Time

Set up real-time Clerk webhook notifications in under 15 minutes. Get instant alerts for new signups, logins, and user changes on Telegram, Discord, Slack, or your phone.

Get Started Free

Related Articles

Frequently Asked Questions

How to Set Up Clerk Webhook Notifications with Webhookify - Webhookify | Webhookify