Skip to main content
A waitlist is an audience that builds itself, but only if you treat it as one. Most teams collect signups for months and send nothing until launch day. By then, many have forgotten they joined. The fix is two emails and one flow. Confirm the signup immediately, check in while they wait, and run a proper sequence when you open the doors. This recipe uses Clerk, whose 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 the waitlistEntry 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 by waitlistEntry.created. Keep it about the signup. No opt-in is on record yet, so this email can’t carry marketing.
Save the demo video or changelog link for the keep-warm email in step 3. That one goes only to contacts who opted in. Set it Live and every new signup gets confirmed within seconds, for as long as the waitlist runs. Two checks before you go live:
  • 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 marketingOptIn with POST /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:
The Filter runs after the Wait. So it reads the opt-in your backend saved, even if that came after Clerk’s event. See Conditions After a Wait. If your wait is long, send fresh progress updates as one-off emails to the waitlist contacts who opted in instead. That keeps the content current rather than frozen in the flow.

4. Launch Day: Run the Sequence

Save an audience of your waitlist contacts who opted in. Clerk waitlist sign-ups arrive with a clerkWaitlistStatus 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:
Test it with Test automation, check the contact count on the trigger node, and run it. The automation shows Sending while the run is in flight and Sent when it completes.

5. After Launch

Two cleanup moves:
  • Retire the waitlist flow. Unpublish the waitlistEntry.created automation 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 it with list_integrations or GET /v1/integrations. From there the recipe runs over MCP:
  • check_trigger shows whether the waitlistEntry.created trigger has received an event, and which published automations consume it.
  • create_email makes each design first. save_automation then saves the confirmation flow and the launch flow, with each send node pinned to one design. test_automation with a testRecipient runs a flow to that address.
  • run_automation launches the launch-day sequence against the saved waitlist audience. Pass dryRun: true first for the count.
If the waitlist lives in your own backend, save_trigger defines the event. Your backend fires it with POST /v1/automations/triggers/{triggerEventId}/fire per signup. To check it first, check_trigger with a sample payload validates the event, and test_automation runs the draft and sends nothing without a testRecipient. fire_trigger_event is a real fire: it starts the published automation and can send email.

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:

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.