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

# Create and Send an Email

> Create a one-off email in Brew from a prompt, edit it, make variants, send a test, and send it to a saved audience now or on a schedule.

Create a one-off email, edit it, try variants, and send it to an audience.

New to Brew? [Send Your First Email](/get-started/send-your-first-email) walks through a first test send. For how groups, canvases, versions, imports, and exports work, see [Emails](/create-emails/emails).

## Create the Email

**1. Describe the email**

Open **Home** and describe what you want in the chat. Be specific about the purpose, the audience, and the tone. The more detail you give, the better the first version.

Some examples:

* *"Write a product launch announcement for our new dashboard feature. Excited tone, one clear CTA to try it."*
* *"Create a spring sale email with a product grid and a code that expires Sunday."*
* *"Draft a re-engagement email for customers who haven't logged in for 30 days."*

**2. Wait for the design**

Brew generates the email on the canvas. From there you can edit it, send a test, create variants, or send it to an audience.

From an agent, a design that is still `generating` comes back with a `runId`. Poll `get_email` with that `runId` until it is ready. Calling `create_email` again starts a second billed design.

**3. Personalize the copy**

Add a [merge tag](/create-emails/merge-tags) like `{{ firstName }}` to address recipients by name or use their own data.

## Edit the Email

Click any email on the canvas to select it. You have two ways to edit:

**Edit with AI (chat).** Use the chat panel for bigger changes:

* *"Make this more direct."*
* *"Add a second version for enterprise buyers."*
* *"Replace the hero with a product screenshot."*

Brew updates the selected email and saves a new version.

**Edit manually.** Click directly into the email to edit text, links, buttons, and images. Manual edits autosave into the current version. They don't create a new one.

> [!WARNING]
>
> A manual edit changes that version in place, including in any published automation that sends it. An AI edit or a restore saves a new version. Automation steps pinned to the old version move onto the new one.
>
> That change lands in a draft automation version you publish when ready. To keep a live automation's email fixed, clone the email and pin the clone.

From an agent, `restore_email_version` restores an earlier version as the new latest one.

<video controls preload="none" poster="/images/posters/edits1.webp" loop muted playsInline>
  <source src="https://0edx89zhjrasqnjf.public.blob.vercel-storage.com/docs/edits1.webm" type="video/webm" />
</video>

## Create Variants

Ask Brew for variants when you want options without losing the original:

* *"Give me a shorter version of this email with a single CTA."*
* *"Make a more playful version of this welcome email."*
* *"Generate a B variant of this announcement with a different hero image."*

Variants appear as separate emails on the canvas. The original stays untouched.

## Send the Email

<video controls preload="none" poster="/images/posters/send_preview.webp" loop muted playsInline>
  <source src="https://0edx89zhjrasqnjf.public.blob.vercel-storage.com/docs/send_preview.webm" type="video/webm" />
</video>

**1. Send a test**

Use **Test** to preview the email in your inbox or a teammate's before sending. A test uses no credits but counts toward your monthly email sends.

From an agent or the API, a test without a `domainId` goes out from Brew's test sender. An unverified domain is refused, never swapped.

**2. Set up the send**

When the email is ready, click **Send** in the toolbar. Pick a saved audience, choose a verified domain, and review sender details.

**3. Choose when it goes out**

* **Send now**: the email goes out right away.
* **Schedule**: set a date and time for the email to go out automatically.
* **Intelligent send**: Brew sends each contact at the hour they're likeliest to open, within 24 hours of your start.
* **Gradual send**: send in batches that grow over hours or days to warm up a new or low-volume domain.

See [Send Options](/create-emails/send-options) for how each option works.

To send the design through HubSpot, Klaviyo, Mailchimp, or another ESP instead, see [Exporting to Another ESP](/create-emails/emails#exporting-to-another-esp).

## From an Agent or Code

From an agent, `create_email` creates the design, and `send_email` sends a test or sends to a saved audience. [Launch a Campaign](/api-reference/mcp/workflows#launch-a-campaign) walks through the review and approval steps.

From code, create the design with `POST /v1/emails` and send it with `POST /v1/sends`. [Send Options](/create-emails/send-options#from-an-agent-or-code) owns the test, audience, scheduling, and send-mode fields.

## Related

* [Emails](/create-emails/emails)
* [Send Options](/create-emails/send-options)
* [Merge Tags](/create-emails/merge-tags)
* [Emails vs Automations](/create-emails/emails-vs-automations)
* [Run Your Email Ops from an AI Agent](/recipes/run-brew-from-an-ai-agent)

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

> **Search Documentation**
>
> Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages.

> **[Ask ChatGPT or Claude](#top)**
>
> Click here to open the **Copy page** menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.

**Talk to Our Team**

> **[Schedule a Call](https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1iYoRUG1J792XQpbuQLjSRRDupr7MwraFK-HQRCtTYdBmrQi8nZu2qXfzKQigb8gbKJK3KN3-R)**
>
> Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.

> **Call Us Directly**
>
> Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions.

> **Slack Channel**
>
> Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses.

> **[Email Support](mailto:support@brew.new)**
>
> Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack.


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