What are Clerk webhooks?
Clerk webhooks send an HTTP request when an event occurs in your Clerk account. Teams use them to react to authentication and user lifecycle events without repeatedly polling an API. Hookflo gives each delivery a searchable record and can notify the right team when an event arrives or signature verification fails.
Events to monitor
Choose the event types that matter in your Clerk configuration. Common examples include:
- user.created
- user.updated
- user.deleted
Connect Clerk to Slack or email
- Create a webhook in Hookflo and select Clerk.
- Copy the unique Hookflo webhook URL.
- In Clerk Dashboard → Webhooks, add the Hookflo URL and choose the event types to send.
- Use the endpoint signing secret shown by Clerk. Clerk webhooks use Svix-style signatures, so the endpoint secret is required to verify each delivery.
- Save the endpoint, send a test event, and choose Slack or email for notifications.
Verify signatures and debug delivery issues
A Clerk endpoint has its own signing secret. Make sure Hookflo has the secret for the same endpoint that sends the event.
When a delivery fails, check the selected event, destination URL, and provider-specific signing secret first. Hookflo keeps the event payload and verification result together so the issue is easier to diagnose.
Read Clerk webhook documentationHow do I monitor Clerk user webhooks?
Create a Clerk webhook endpoint that points to your Hookflo URL, select user events, save its signing secret in Hookflo, then enable Slack or email notifications.