Automations are emails Brew sends in response to events in your business, such as a signup, purchase, or payment failure. This page is the reference for the automation builder and the data it uses.
For the difference between one-off Emails and Automations, see Emails vs Automations. To create and publish a flow, follow Build an Automation.
The Automations List
The Automations list shows every automation with its status and trigger, plus counts for total, live, and draft flows. Search automations, manage trigger events with Triggers, or start a flow with New automation. Click an automation to open its dedicated canvas. The canvas always shows the flow selected from the list. Here the container is the automation itself, the same list-then-canvas pattern Emails use with groups; see Canvases.Node Types
Every flow starts with a trigger. The + menu offers six choices for the steps that follow. Send Email. Sends an email to the contact moving through the flow. The node can generate a new email or reference an email design from another flow. Each contact that reaches a Send Email node produces one send with its own delivery and engagement events. Those sends appear in analytics alongside one-off sends. Personalize with contact properties such as{{ firstName }} or trigger values such as {{ orderId }}.
Wait. Pauses the flow before the next node. Choose a preset duration, such as 1 hour, 1 day, 3 days, or 1 week, or enter a custom value.
Filter. Continues a contact only when a condition matches. Conditions can use contact properties, behavior such as opening a previous email, or trigger payload data. contact.plan reads the contact’s saved plan field, and a bare name such as orderId reads the trigger payload.
Split. Creates two paths based on contact or event data, such as the contact’s plan or a trigger payload value.
A/B Split. Sends a chosen share of contacts down each path. Use 50/50 to compare two versions, or choose another split.
Engagement. Routes contacts by opens, clicks, or a specific link in an earlier email in the same flow. Set a waiting window before checking. This checks engagement inside a flow; it does not make opens or clicks a start trigger.
Conditions After a Wait
A Filter or Split oncontact.<name> reads the contact’s saved value when that node runs. After a Wait, that’s the contact’s current value, not the value when the flow started. Trigger payload fields keep the values the event sent.
Updating a contact during a Wait doesn’t stop the flow, and later conditions see the new value. To skip a reminder for someone who already acted, update a contact field when they act. Then check that field after the Wait.
When the Same Event Fires Again
Each accepted event starts its own run. A retry with the same idempotency key returns the original run instead of starting another. See Idempotency. If the event fires again for a contact already partway through, Brew starts a second run. The first run keeps going on its own schedule. The new event also saves its fields onto the contact, so later conditions in both runs see those values. If your app can send the same event twice, the contact can receive the flow’s emails twice. A Filter can’t see earlier runs, so it can’t stop a repeat entry. Send each event once, or start the flow from an event that fires once per contact.Send Marketing Only to Contacts Who Opted In
A sign-up, purchase, or waitlist join isn’t marketing consent. Ask for opt-in where the person signs up, such as with an unticked checkbox. Then get the answer onto the contact:- Custom event. Send it in the payload, for example
"marketingOptIn": true, and declare it on the trigger. Brew saves declared top-level fields on the contact before the flow starts. - Integration trigger. Save it as a contact property, such as
marketingOptIn, from your backend withPOST /v1/contacts. A Filter right after the trigger reads the contact as the flow starts. So save the property before the provider’s event fires, or use a custom event instead.
contact.marketingOptIn. The contact. prefix matters, because a bare marketingOptIn reads the trigger payload. Provider payloads, such as Clerk’s and Stripe’s, carry none. See What You Can Send for what counts as consent.
Emails Used in an Automation
An email in the email canvas can be the email a Send Email node sends. When it is, Brew marks it in the canvas: the email’s header shows a small automation icon in the top right corner, with a count of how many automations use it. Click the icon to see which ones. The popup lists each automation that sends this email, with its state (Draft or Live) and the email version that automation is pinned to. Select a row to open that automation’s canvas. The icon appears for draft and published automations alike, so an email can be linked before the flow ever goes live.Lifecycle States
Each save or edit creates a version, shown in the canvas header as a version chip such as
v4.
Editing a Live automation saves a new draft version, and the published version keeps serving until you publish again. Over the API, that update returns a DRAFT_SAVED_NOT_LIVE warning, and liveVersion names the version that is serving.
Unpublishing keeps history and returns a live flow to Draft. New people stop entering, and anyone already partway through still finishes.
Pausing holds a live flow’s sends, for everyone, until you resume it. To pause a manual-audience automation, pause its run instead.
A pause has a limited window. When it closes, Brew sends you a notification, and events that arrive after that are skipped instead of starting a run. Resume before then if you want new contacts to enter the flow.
Personalization
Merge tags pull contact properties ({{ firstName }}), custom properties ({{ plan }}), and trigger payload fields ({{ orderId }}) into email content. Merge Tags owns the full syntax, the fallback form, and the rules for what resolves.
Triggers
Every flow starts with a trigger. It can be a custom event from your backend, an event from a connected source, an unsubscribe, or a saved audience run on demand. Automation Triggers is the reference for each one. It covers payload contracts, what a fire saves on the contact, and validation errors.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.