waitlistEntry.created event fires the moment someone joins.
Before you start. You need a verified sending domain and a Clerk application with the waitlist feature enabled. If your waitlist lives elsewhere, fire a custom event from your backend instead; the rest of the recipe is identical.
1. Connect Clerk
Follow the Clerk integration setup. Paste the brand-scoped webhook URL into Clerk and enable thewaitlistEntry events. Confirm a test event lands in the Manage → Recent events panel.
Every Clerk event also upserts the person into your audience. Your waitlist contacts accumulate in Brew without an import step.
2. Confirm the Signup Instantly
Build a single-email automation triggered bywaitlistEntry.created. Keep it about the signup. No opt-in is on record yet, so this email can’t carry marketing.
- Ask for the opt-in. Joining a waitlist isn’t marketing consent, and Clerk’s event carries no opt-in field. Add an unticked opt-in checkbox to the waitlist form. Have your backend save the answer as
marketingOptInwithPOST /v1/contacts. Send the keep-warm and launch emails only to contacts who ticked it. Send Marketing Only to Contacts Who Opted In has the details. - Avoid two confirmations. Clerk can send its own waitlist confirmation. Turn it off or customize it in Clerk, so signups don’t get both.
3. Keep Them Warm While They Wait
A silent waitlist decays. Add a second email to the same flow, two to three weeks after the first, sharing real progress. It’s marketing, so put a Filter on your opt-in property in front of it:4. Launch Day: Run the Sequence
Save an audience of your waitlist contacts who opted in. Clerk waitlist sign-ups arrive with aclerkWaitlistStatus of pending, so filter on that and marketingOptIn.
Then use a one-off flow rather than a single send. The flow gives you a built-in follow-up for the people who miss the first email:
5. After Launch
Two cleanup moves:- Retire the waitlist flow. Unpublish the
waitlistEntry.createdautomation once the waitlist closes, or leave it live if you’re still gating access. - Hand off to onboarding. New users now arrive through
user.created, so point a welcome flow at that event and let the regular lifecycle take over.
From an Agent or Code
Connecting Clerk is app-only. An agent can confirm the connection, and over the APIGET /v1/integrations does the same. From there the recipe runs over MCP:
- The agent can show whether the
waitlistEntry.createdtrigger has received an event, and which published automations consume it. - It makes each design first. It then saves the confirmation flow and the launch flow, with each send node pinned to one design.
- A test with a test recipient runs a flow to that address.
- It launches the launch-day sequence against the saved waitlist audience. Ask for a dry run first to get the recipient count.
“Do a dry run of the launch-day flow against the waitlist audience and tell me the recipient count.”If the waitlist lives in your own backend, the agent can define the event. Your backend fires it with
POST /v1/automations/triggers/{triggerEventId}/fire per signup.
To check the event first, ask the agent to validate a sample payload against it. A test of the draft sends nothing unless you name a test recipient. Firing a real event is different: it starts the published automation and can send email.
Related
- Clerk: events, merge tags, and the webhook setup.
- Run a One-Off Flow: the launch-day flow in detail.
- Build a Welcome Flow: the flow that takes over after launch.
- Automations: custom trigger events for a waitlist outside Clerk.
- What You Can Send: why the waitlist form needs its own opt-in.
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.