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

# Brew in Slack

> Mention @Brew in a Slack thread to draft, test, and schedule email. Anything that reaches real people waits for an approval card only you can answer.

<Note>
  **October 2026**
</Note>

<Note>
  **Historical note · October 2026** · Describes Brew as of October 2026. For
  current behavior, see [Slack](/integrations/import/slack).
</Note>

## What Shipped

Most launch emails start in a Slack thread. Forty messages later, someone
rebuilds the whole conversation by hand in the email tool.

Now Brew works in the thread. Mention **@Brew** and it drafts the email where
the team can see it. The reply carries a picture of the design.

When it's time to send, it posts an approval card. Nothing reaches a real
inbox until the person who asked clicks **Approve**.

## How It Works

<Steps>
  <Step title="An admin installs Brew once">
    Open **Integrations → Slack**, click **Connect**, and approve the app in
    Slack. One install covers the whole organization.
  </Step>

  <Step title="Everyone links their own account">
    The first time you mention @Brew, it sends you a private one-time link.
    Open it while signed in to Brew, and Brew answers your original message.
  </Step>

  <Step title="Brief it in a thread">
    "@Brew draft the October update for Pro customers. Under 150 words."
    Revise in the same thread like you would with a teammate.
  </Step>
</Steps>

Every thread is also a chat in the Brew web app. Layout work on the canvas
picks up where Slack left off.

## Only the Person Who Asked Can Approve

Anything that reaches other people waits for a card first:

* a send or a schedule;
* a test to anyone but you;
* an automation run;
* a resume or a cancel.

The card shows the email, how many recipients are eligible, the sender, the
subject, and the send time.

Only the person who wrote the brief can answer it. They read the preview and
checked the audience. A teammate scrolling past can't send to 40,000 people
with one click.

A test to yourself and a pause skip the card, since neither reaches your
audience.

## Results Where the Team Reads

Pick a channel in **Integrations → Slack**. It gets a post for each send, a
weekly overview every Monday, and comment mentions on the brand's emails. Each
brand can post to up to 10 channels.

## Get Started

Ask an organization admin to connect Slack from **Integrations**, then mention
@Brew in a thread. [Slack](/integrations/import/slack) covers setup, approvals,
and notifications.


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