- Events. A signup can start a published automation, such as a welcome email.
- Contacts. Signups, profile updates and waitlist entries add or update the person in your audience, with
clerkfields.
How It Connects
Clerk sends the events selected on its webhook endpoint to Brew. Auser.created event can start a published automation that uses Clerk - User Created.
A user.updated event can update the contact even when no automation uses that trigger. Recent events marks each verified delivery signature ok.
Requirements
- A Clerk instance and a Brew brand.
- A Clerk webhook endpoint that points to Brew and subscribes to the events you want Brew to receive.
Setup
Connect Clerk in Brew, then point a webhook endpoint in Clerk at Brew. To check an existing connection, open Webhooks in Clerk and select the endpoint that points to Brew. Check its event subscriptions. For profile updates, adduser.updated if it’s missing. Adding the event to the endpoint is enough for Brew to receive it.
Events
Brew has a trigger for 17 Clerk events. Each one declaresemail as a required string and createdAt as an optional integer. They also declare firstName and lastName as optional strings.
Use these fields as merge tags. The trigger’s payload contract lists its exact fields.
The integration’s Events list shows Last event for each event Brew has received. The rest read Not received yet.
Contacts
Brew can create a contact on signup or waitlist entry. A Clerk profile update can change the first name on an existing contact. Turn on Clerk’s First and last name setting to collect names on the hosted signup form. Brew can then store them asfirstName and lastName. An email-and-password-only signup can leave both fields absent.
Clerk signup and waitlist events can create contacts that are subscribed, with no consent record. Confirm the person opted in before you send marketing email.
Check It Works
- Open the Clerk integration in Brew. Check for Connected and a Webhook secret ending line.
- Check which published automations use Clerk - User Updated. Then change a test user’s name in an instance with
user.updatedsubscribed. - In Events, look for Last event on
user.updated. In Recent events, look for the receipt with signature ok. - Open the Brew contact and check that the changed name arrived.
Common Patterns
- Welcome new users. Use Clerk - User Created for your signup automation. Use
firstNameto personalize the subject and body when your signup form collects names. - Track waitlist signups. Look for
waitlistEntry.createdwhen someone joins the hosted waitlist. The contact can haveclerkWaitlistStatusset topending.
Limits
- Receipts. A receipt shows its processing state and the runs it started, not the event’s values. Read the payload contract for declared fields and the contact for stored values.
Troubleshooting
An event reads Not received yet
An event reads Not received yet
In Clerk Webhooks, check that the endpoint pointing to Brew subscribes to that event.
A receipt reads 0 matched · 0 started
A receipt reads 0 matched · 0 started
Check the published automations that use the trigger. A receipt can read
fired even when no run starts.A welcome email is missing
A welcome email is missing
Check the run and its email step. The run can complete with the email step marked
skipped when the recipient doesn’t match the filter.In Analytics, look for Sent and Delivered with Clerk - User Created in the Source column.From an Agent or Code
Connecting Clerk is app-only. After that, an agent connected over MCP can check deliveries and build automations. Ask in plain English:“Has Brew received a user.created event from Clerk, and did it start a run?”
“Build a welcome automation on Clerk User Created and test it as a draft without sending email.”From code:
GET /v1/integrationsshows whether Clerk is connected.GET /v1/automations/triggers/{triggerEventId}/readinessreturnsdelivery. Once Brew has seen the event,delivery.statusreadsreceivedanddelivery.lastReceivedAtgives the latest arrival.GET /v1/automations/trigger-instanceslists each receipt with its state and the runs it started.GET /v1/automations/triggers/{triggerEventId}/contractreturns the trigger’s declared fields.
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.
Ask ChatGPT or Claude
Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.