Skip to main content

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.

A welcome flow is the highest-leverage automation you can build. It runs once, reaches every new signup at exactly the right moment, and compounds over time as your list grows. This recipe walks through building a 3-step welcome flow triggered by a new user signup. The same pattern works for newsletter subscribers, trial users, or any other entry point.

​
Before you start

You need a verified sending domain. See Verify your sending domain.

​
1. Set up your trigger

You have two options depending on your stack. Option A: Use an integration. If you use Stripe or another connected platform, Brew can use their events as triggers directly. Connect your integration in Integrations and the relevant events become available in the automation builder. For a welcome flow, customer.subscription.created is the most common Stripe trigger — it fires the moment someone starts a subscription. Check the integrations page for the full list of supported platforms and their available events. Option B: Custom event. If you want to trigger from your own backend, Brew can create the trigger event for you as part of generating the flow. Just describe it in your prompt in step 2 and Brew sets it up. Once the flow is generated, wire up the event in your backend via the API Reference.

​
2. Generate the flow

Open Home and describe what you want in the chat. A simple prompt is enough: 
Build a 3-email welcome flow triggered by a new user signup.
Or be more specific to get a better first version: 
Build a 3-step welcome flow triggered by user_signup.

Email 1: welcome them and set expectations. Tell them what the product does,
what they can expect over the next few days, and the single most
important first action to take. Warm, direct tone.
Wait 2 days.
Email 2: a quick-start tip for the feature most new users miss.
Practical, specific, one clear next step.
Wait 3 days.
Email 3: a short customer story showing what success looks like.
End with an offer to help directly — a reply, a call, or a link to support.
Brew opens the flow editor with the trigger, all three emails, and the wait nodes already in place. Review the diagram on the right to confirm the structure looks right before editing anything.

​
3. Review and edit each email

Click any Send Email node in the diagram to open that email. You have three ways to refine it: Edit with AI via the flow chat. Use the chat panel on the left to make changes across the whole flow or to a specific email:
  • “Make the first email shorter and more direct.”
  • “Add the recipient’s first name to the subject line of email 2.”
  • “Make email 3 feel less like a case study and more like a quick story.”
Edit with AI via Add to chat. Click the email node to select it, then click Add to chat in the toolbar. This brings that specific email into the chat so you can focus your edits on it without affecting the rest of the flow. Edit manually. Click directly into the email to adjust text, links, buttons, and images. Manual edits autosave. To personalize with the contact’s name, use {{{firstName}}} anywhere in the email body or subject line. If no name is available, add a fallback: {{{firstName | there}}} renders as “Hi there” when the field is empty.

​
4. Test the flow

Test at two levels before publishing. Individual emails. Click any Send Email node in the flow diagram, then click Test in the toolbar. A preview modal opens — enter one or more email addresses separated by commas and click Send Preview. The subject line is prefixed with [PREVIEW] so it’s easy to spot in your inbox. Preview emails don’t affect analytics. The full flow. Once individual emails look right, open the flow and click Test automation. Enter a test email address and fill in the trigger payload fields — these are the values Brew uses to personalize the emails during the test run. Click Fire test. Brew runs through the entire flow exactly as a real event would, sending all emails to the test address only. Real contacts on the trigger payload are never hit on test runs. Recent test runs appear at the bottom of the modal so you can confirm the flow fired correctly.

​
5. Publish

When the flow looks right, open the lifecycle status dropdown and change it from Draft to Published. The next matching trigger event will start the flow automatically. Monitor runs from the Automations dashboard. It shows Active, Runs, Sent, and Issues across all flows. Click into this flow to see individual execution history and catch any failures early.

​
Extending the flow

Once the 3-step flow is running, common additions include: A split based on engagement. After email 2, split the flow: contacts who clicked go down a deeper product education path, contacts who did not get a simpler re-engagement nudge. 
Add a Split node after email 2. Path A: contacts who clicked the CTA.
Send them a more advanced tip about [feature]. Path B: contacts who
did not click. Send a simpler "here's what most people do first" email.
A trial expiry reminder. If you have a trial period, add an email triggered a few days before it ends. 
Add a fourth email 5 days after email 3. Remind them their trial ends
in 48 hours. One clear CTA to upgrade. Confident, not pushy.
The flows you can build are only limited by what your business needs. A single prompt gets you started and the agent handles the rest — triggers, emails, waits, splits, all of it. See Automations for the full list of node types and what’s possible.