Clerk Webhooks
Build event-driven features by listening to Clerk authentication and organization events through webhooks. Verify every webhook using the framework-specific verifyWebhook function, then sync data to your database, send notifications, or trigger downstream integrations. Complete working examples show how to handle user lifecycle events, organization membership changes, and multi-service workflows like welcome emails and Slack alerts.
Clerk Webhooks lets you build event-driven features by handling real-time Clerk authentication and organization events with signature verification.
AI-generated summary based on this skill's SKILL.md
Install
clerk/skills/clerk-webhooks · repository language: Shell
git clone https://github.com/clerk/skills
cp -r skills ~/.claude/skills/clerk-webhooksgenerated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
npx skillfed install clerk/skills/clerk-webhooksFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I configure Clerk webhooks?
Clerk Webhooks lets you configure webhook endpoints to receive real-time notifications when authentication and organization events occur. Start by creating an endpoint URL in your application, then register it in the Clerk Dashboard under Webhooks. Clerk will send signed POST requests to your endpoint whenever events like user.created, user.updated, or organization.membership.created are triggered. Always verify the webhook signature using the framework-specific verifyWebhook function before processing the payload.
What event types does Clerk Webhooks support?
Clerk Webhooks supports a comprehensive set of user lifecycle and organization events. Common events include user.created, user.updated, user.deleted for user management, and organization.created, organization.membership.created, organization.membership.updated for organization changes. Each event includes a detailed JSON payload with all relevant data. The payload structure is consistent across event types, making it easy to parse and route events to your database, notification systems, or downstream integrations.
How do Clerk webhooks work for real-time integrations?
Clerk Webhooks delivers real-time event notifications to your configured endpoints, enabling event-driven architectures. When a user signs up or updates their profile, Clerk immediately sends a signed webhook payload to your listener. You can then sync data to your database, send welcome emails, trigger Slack alerts, or update external systems. This approach eliminates polling and keeps your application synchronized with Clerk's authentication state in real time.
How should I set up webhooks in Clerk for security?
Clerk Webhooks includes built-in security through signed payloads. Every webhook request includes a signature header that you must verify using Clerk's verifyWebhook function before trusting the data. This prevents unauthorized requests from triggering your integrations. Additionally, store your webhook signing secret securely as an environment variable, never commit it to version control, and validate that incoming requests match your expected event types before processing them.
Can I integrate Clerk webhooks with external systems?
Yes, Clerk Webhooks is designed for multi-service workflows. After verifying a webhook, you can trigger actions across your entire stack: sync user data to your database, send emails via SendGrid or Mailgun, post notifications to Slack, update CRM systems, or trigger serverless functions. The consistent JSON payload structure makes it straightforward to extract data and route it to any external API or service, enabling complex event-driven automation.
What should I do if Clerk webhooks aren't being delivered?
Clerk Webhooks provides debugging tools to troubleshoot delivery issues. Check the Webhooks dashboard for delivery logs and retry attempts. Verify your endpoint URL is publicly accessible and returns a 2xx status code. Ensure you're verifying signatures correctly—signature mismatches often indicate timing or secret key issues. Test with Clerk's webhook testing feature to send sample events. If problems persist, confirm your endpoint isn't rate-limiting Clerk's requests and that firewall rules allow inbound traffic.