Clerk Source Configuration

Clerk configuration

Create a Clerk source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Clerk delivery before it enters the routing workflow.

{
  "type": "CLERK",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "CLERK",
      "webhook_signing_secret": "whsec_..."
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Clerk request contract

FastHook uses Svix verification over message id, timestamp, and raw body with the configured whsec secret.

Clerk headers

Preserve svix-id, svix-timestamp, svix-signature when sending Clerk test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Clerk setup

1. Create a Clerk webhook endpoint with the FastHook Source URL.
2. Copy the Clerk whsec signing secret into FastHook.
3. Route by event type such as user.created or organization.updated.

Clerk routing hints

• Clerk identity traffic usually branches by event type, such as user.created, session.created, or organizationMembership.created.
• Route organization and user identifiers together when downstream systems need to update membership, access, or customer records.

Continue with Clerk

• Clerk webhooks documentation
• Source operations and troubleshooting