Connect Clerk to Brew so user, organization, billing, and waitlist events fire automations. Send a welcome email when someone signs up, drip a dunning sequence when a subscription goes past due, kick off a workspace-onboarding flow when a new team gets created.Documentation Index
Fetch the complete documentation index at: https://docs.brew.new/llms.txt
Use this file to discover all available pages before exploring further.
What you can do
- Trigger automations from Clerk events. Kick off email flows when users sign up, orgs are created, subscriptions go past due, or waitlist entries arrive
- Auto-sync contacts into your audience. Every Clerk event upserts the user into Brew with
clerk_*custom fields (clerk_user_id,clerk_subscription_status,clerk_plan_name, …) you can filter and segment on - Personalize with auth context. Reference
firstName,lastName,planName,organizationName, and other Clerk fields inside emails - Cover lifecycle + billing in one place. Onboarding, dunning, win-back, and waitlist nurture all use the same Clerk connection
How it works
- Brew mints a unique webhook URL for your brand and you paste it into your Clerk Dashboard.
- Clerk signs every webhook with your endpoint’s signing secret. Brew verifies the signature via the Standard Webhooks (Svix) spec on receipt — tampered or replayed events are rejected.
- For each verified event Brew (a) starts every matching automation and (b) upserts the Clerk user into your audience with
clerk_*custom fields.
Setup
Generate your Brew webhook URL
In Brew, open Integrations, click the Clerk card, and click Generate URL. Copy the URL Brew generates for the next step.
Add an endpoint in Clerk
Open dashboard.clerk.com, go to Webhooks → + Add Endpoint, and paste the Brew URL into the Endpoint URL field.
Subscribe to the events Brew supports
Enable the user, organization, organizationInvitation, organizationMembership, paymentAttempt, subscription, subscriptionItem, and waitlistEntry events (full list below), then click Create.
Reveal the Signing Secret
On the endpoint detail page Clerk shows next, click the eye icon next to Signing Secret to reveal it. The value starts with
whsec_.Paste the Signing Secret into Brew
Paste the
whsec_… secret into the Brew connect form and click Connect. Brew verifies every webhook using the Standard Webhooks (Svix) spec.Brew only listens for Clerk events. It can’t modify users, create organizations, or charge subscriptions.
Triggering automations
Once connected, Clerk events show up as available triggers in the automation builder. Open the Manage tab in the Clerk integration to enable the specific events you want to fire automations — every event is disabled by default to keep things quiet.Supported events
Brew supports the following 13 Clerk events as automation triggers: Useruser.created
organization.createdorganizationInvitation.createdorganizationInvitation.acceptedorganizationInvitation.revokedorganizationMembership.created
paymentAttempt.createdsubscription.createdsubscriptionItem.freeTrialEndingsubscriptionItem.pastDuesubscriptionItem.canceledsubscriptionItem.abandoned
waitlistEntry.created
Common patterns
| Goal | Clerk event |
|---|---|
| Welcome new user | user.created |
| Workspace-setup checklist for new orgs | organization.created |
| Branded “you have been invited” email | organizationInvitation.created |
| Welcome new teammate | organizationInvitation.accepted or organizationMembership.created |
| Pre-charge heads-up to reduce chargebacks | paymentAttempt.created |
| Trial-ending reminder | subscriptionItem.freeTrialEnding |
| Dunning sequence on missed payment | subscriptionItem.pastDue |
| Exit survey / win-back drip on cancel | subscriptionItem.canceled |
| Last-chance offer when a trial ends without payment | subscriptionItem.abandoned |
| ”You’re on the list” + nurture drip | waitlistEntry.created |
Personalization
Use Clerk payload fields anywhere in your emails. Common variables:| Variable | Example |
|---|---|
{{@trigger:output.payload.firstName}} | Jane |
{{@trigger:output.payload.lastName}} | Doe |
{{@trigger:output.payload.planName}} | Pro Plan |
{{@trigger:output.payload.planAmount}} | 2000 (Clerk sends amounts in the smallest currency unit — cents for USD) |
{{@trigger:output.payload.organizationName}} | Acme Corp |
{{@trigger:output.payload.grandTotalFormatted}} | $22.00 (already pre-formatted by Clerk) |
Clerk organization events (like
organization.created) don’t carry a customer email. Brew emits a synthetic placeholder so you can still route the event internally; use createdBy if you want to reach the org’s creator.Troubleshooting
An event arrived but no automation fired
An event arrived but no automation fired
Brew provisions every Clerk event disabled-by-default so production noise stays low. Open the Clerk integration in Brew, go to the Manage tab, and toggle the event ON. Then make sure at least one of your automations uses it as a trigger and is set to Published (not Draft).
Clerk shows 401 on every delivery
Clerk shows 401 on every delivery
The signing secret in Brew doesn’t match the one in Clerk’s Dashboard — usually because it was rotated in one place but not the other. Reveal the current secret on the Clerk endpoint detail page and re-run setup step 5 in Brew.
I want to test before going live
I want to test before going live
Create a Draft automation, run a test send from the email editor, and only flip the automation to Published once you’re happy. The Manage → Recent events panel shows every webhook Clerk has delivered in the last 24 hours so you can verify the trigger is firing the way you expect.
Requirements
- A Clerk account on any paid plan (free instances support webhooks too)
- Admin access to your Clerk Dashboard so you can add a Webhook endpoint and reveal the Signing Secret
Need Help?
Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:- Self-Service Tools
- Talk to Our Team
Search Documentation
Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.
ChatGPT/Claude Integration
Click “Open in ChatGPT” at the top right of any page to analyze documentation with ChatGPT or Claude for deeper insights.