Integration · Clerk
Verified Clerk webhooks for your AI agent.
Hooksbase verifies each Clerk webhook signature before persisting the delivery, stamps queryable provider metadata (event type, source ID, verified flag) on the event, and routes it to your AI agent — no webhook plumbing to build.
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.
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
Route `user.created` to an agent that personalizes onboarding, sends a welcome, and provisions workspace state.
Route `user.updated` with email changes to an agent that double-checks for suspicious activity.
Fan-out `session.*` events to an analytics destination alongside a lightweight agent for anomaly detection.
Frequently asked questions
- How do I verify Clerk webhooks with Hooksbase?
- Clerk signs webhooks with a Svix-compatible scheme. Add the Clerk provider pack to a Hooksbase webhook and paste your Clerk signing secret; Hooksbase verifies the Svix signature before the delivery is persisted, so only authentic Clerk events reach your agent.
- Does Hooksbase check the Clerk signature before my agent sees the event?
- Yes. Hooksbase validates the Svix-compatible signature before persisting the delivery and marks `provider.verified = true`. Your agent never sees a Clerk event that failed signature verification.
- Which Clerk event types can I route on with Hooksbase?
- Hooksbase extracts the Clerk event type into `provider.eventType` (for example `user.created` or `session.ended`), so you can route user-lifecycle events directly. The Svix message ID is captured as `provider.sourceId`.
- Can I send Clerk events to multiple destinations from Hooksbase?
- Yes. Hooksbase can fan a single verified Clerk event out to several typed destinations at once — for example an onboarding agent over HTTP plus an analytics sink — each with the full provider metadata attached.
- Can I replay a Clerk webhook delivery in Hooksbase?
- Yes. Hooksbase retains delivery detail for 30 days and supports deterministic replay from the persisted dispatch snapshot, so you can re-run a verified Clerk `user.created` event through your agent after fixing onboarding logic.
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.