What problem does it solve? Building webhook endpoints for Clerk authentication events requires correct signature verification, public route configuration, and framework-specific request handling, and mistakes lead to 401 errors, spoofed events, or missed database syncs. ## Core Features & Use Cases - Verified Webhook Handlers: Generate complete handlers using verifyWebhook from framework-specific packages like @clerk/nextjs/webhooks and @clerk/express/webhooks, with automatic CLERK_WEBHOOK_SIGNING_SECRET reading. - Full Event Catalog Coverage: Handle user, session, organization, organization membership, subscription, subscription item, and payment attempt events with typed payload field references. - Framework Support: Ready-made handler patterns for Next.js, Express, Astro, Fastify, Nuxt, React Router, and TanStack Start, including Express raw-body parsing and middleware exclusion rules. - Use Case: Sync new signups to a Postgres users table via Prisma, send welcome emails through Resend, and post Slack notifications whenever a user.created event fires. ## Quick Start Set up a verified Clerk webhook handler in my Next.js app that syncs user.created events to my database.