Skip to main content
Brew has two places to build: Emails and Automations. Three words cover how they fit together:
  • Email. The design: layout, copy, and imagery, made on a canvas in Emails. It carries no send state. Other tools call this content or a template.
  • Campaign. Sending an Email once, to an audience or a list of addresses, now or at a time you pick.
  • Automation. A flow that sends Emails one contact at a time when its trigger fires, like a signup or a purchase. It keeps running until you pause or unpublish it.
So you build an Email, then send it as a campaign or through an Automation.

Send a Campaign When

  • You want to send something to a list of people at a specific time
  • The send is intentional and one-off: an announcement, a promo, a newsletter
  • You’re scheduling in advance: “Send this next Tuesday at 9am”
Examples: product launch announcement, Black Friday promo, monthly newsletter, event invite, re-engagement send.

Use an Automation When

  • You want to send in response to something that happens: a signup, a purchase, a cancellation
  • The email needs to go to one person, at the right moment, automatically
  • You want a multi-step sequence that runs over time without you touching it
Examples: welcome flow, onboarding drip, abandoned cart, payment failed dunning, win-back.
One exception to the “keeps running” rule: a manual-audience automation runs a saved audience through the flow on demand. You get the structure of a flow (waits, filters, splits) with the one-off nature of a campaign. See Manual audience.

One Design, Many Sends

The email itself is a design: the layout, copy, and imagery. A design has no idea whether it’s a one-off send or an automation, and it carries no send state. The same design can go out as a campaign today and be referenced by an automation tomorrow. Nothing about the email changes. What differs is the send, the act of delivering that design to real people. Every time Brew delivers a design, it records one send:
  • A campaign records a single send, scoped to the audience you picked. One send row covers the whole blast.
  • An Automation records one send per recipient: each contact that flows through a Send Email step gets their own send, fired at their own moment.
Both kinds of send land in the same place, tagged as either a campaign send or an automation send. That’s why your analytics line up across both. Opens, clicks, and bounces all attach to the send that produced them, no matter which surface created it.

Where You’ll See Campaign

The sidebar has no Campaigns page. A campaign starts when you send an Email, from the app, chat, the API, or MCP. The word shows up where Brew reports on sends:
  • Analytics. The Campaign tab lists one-time sends, and the summary line counts campaign sends. See Reading Analytics.
  • The API. Every send carries kind: campaign or kind: automation, and GET /v1/sends lists campaign sends by default. See Monitor Campaign Sends.
  • Brew Insights. Insights can suggest a campaign, or flag one whose numbers look off. See Brew Insights.

You Don’t Have to Choose Upfront

Brew figures it out from your prompt. Describe what you want, and Brew routes you to the right type automatically.
  • “Send a Black Friday email next Tuesday” → Campaign
  • “When someone signs up, send a 3-step welcome flow” → Automation
  • “Write a product update newsletter for this week” → Campaign

A Note on Transactional Emails

Transactional emails, such as password resets and receipts, are automations too. What makes one transactional is its sending domain: a transactional-purpose domain skips the unsubscribe link and reaches unsubscribed contacts. Transactional Email covers setup, firing, and what to know before you ship one.

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.