> ## 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.

# Flows: Real Email Sequences to Remix

> Real signup and newsletter sequences from other brands, with the day each email landed. Remix one into a draft automation with the same timing.

<Note>
  **September 2026**
</Note>

<Note>
  **Historical note · September 2026** · Describes Brew as of September 2026.
  For current behavior, see [Remix a Flow](/create-emails/templates#remix-a-flow).
</Note>

## What Shipped

Planning a welcome sequence used to mean guessing the gaps. A template gallery
shows you one good email at a time.

It can't show you that the third email lands on day two. Or that the
trial-ending email follows the "need help?" one by a few hours.

Flows show the whole sequence. Each one is a real brand's signup or newsletter
emails, in order, with the day each one landed.

Remix one you like, and Brew builds a draft automation with the same timing.
Every email is written for your brand.

## What's in a Flow

Every step carries its subject, preview text, the day it landed, and the wait
since the email before it. Read the waits, not just the subjects. They show
where a brand sends on consecutive days and where it backs off.

At launch, the gallery held 151 flows from 151 brands, 1,311 emails in all.

## Remix One

<Steps>
  <Step title="Open a flow">
    Go to **Templates**, open the **Flows** tab, and pick a sequence. Step
    through its emails and the waits between them.
  </Step>

  <Step title="Tell Brew what's different">
    Describe your tone, offer, or audience in the **Remix** box on the flow.
  </Step>

  <Step title="Review the draft automation">
    The timing is copied: the source's gaps become Wait steps, rounded to the
    nearest hour. Each email is rewritten for your brand. Read every one before
    you publish.
  </Step>
</Steps>

## From an Agent or Code

An agent can read every flow without anyone clicking through the gallery.
`list_flows` and `get_flow` over MCP, or `GET /v1/flows` and
`GET /v1/flows/{slug}` from code, return the same sequences.

Each step carries an `emailId`. Pass it as `referenceEmailId` to
`create_email` to build your own version of that one email.

## Get Started

Open **Templates** and pick the **Flows** tab.
[Remix a Flow](/create-emails/templates#remix-a-flow) covers the details.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.