Integration · Clerk

Verified Clerk webhooks for your AI agent.

Clerk uses a Svix-compatible signature scheme. Hooksbase verifies signatures and extracts event type into `provider.eventType` so routing rules can match on user lifecycle events.

Start freeProvider verification guide

Verification + metadata

What your agent receives

// Hooksbase verifies Svix-compatible signature automatically
// Your agent receives:
{
  "provider": {
    "name": "clerk",
    "sourceId": "msg_...",
    "eventType": "user.created",
    "verified": true
  },
  "payload": { /* raw Clerk event */ }
}

Routable metadata fields

Match on provider fields

Once Clerkverification is enabled, these fields are available to routing rules, delivery search, and your agent's payload.

  • provider.name = "clerk"
  • provider.sourceId = Svix message ID
  • provider.eventType = e.g. "user.created", "session.ended"
  • provider.verified = boolean

Agent recipes

Common Clerk + agent patterns

Onboarding agent

Route `user.created` to an agent that personalizes onboarding, sends a welcome, and provisions workspace state.

Account recovery agent

Route `user.updated` with email changes to an agent that double-checks for suspicious activity.

Session lifecycle analytics

Fan-out `session.*` events to an analytics destination alongside a lightweight agent for anomaly detection.

Get started

Point Clerk at Hooksbase.

Configure the Clerk provider pack on a Hooksbase webhook, copy the ingest URL, paste it into your Clerk webhook settings. Every verified event lands with full provider metadata on the delivery.

Start freeRead the verification guide