> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# Connect your app to Brevo

> Use your Brevo account for email, contacts, campaigns, and supported SMS or WhatsApp messaging in your app.

[Brevo](https://www.brevo.com/) is a customer communication platform for email, contacts, campaigns, and messaging. Connect it to Mythos when you want app activity to reach your customers through the channels you already manage in Brevo.

Use the saved connection in the project chat while building and in the app you publish. Your Brevo API key connects your own account; [Connections in Mythos](/integrations/introduction) explains how to share it with teammates and use it in a project.

With Brevo, you can:

* Send transactional email and work with email campaigns.
* Read, create, and update contacts and lists.
* Send SMS and WhatsApp messages when those channels are available in your Brevo account.
* Read email and SMS statistics to build a reporting view.
* Work with Brevo CRM companies, deals, and tasks.

Brevo is useful when contacts, campaigns, and messages belong in the same account. Connecting it does not purchase a Brevo plan, enable a channel, or add sending credits.

## Examples to build

These are apps Mythos can build using your Brevo connection. Describe the trigger, recipient, and content so the resulting workflow matches your business.

| App idea               | Prompt to try                                                                                                                          | What it adds                                                                     |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Order updates          | *Send a Brevo confirmation email after an order succeeds, then a shipping email when staff mark it dispatched.*                        | Messages tied to actual order events in your app.                                |
| Outreach workspace     | *Build a lead dashboard that updates contact attributes and list membership in Brevo, with a review screen before sending a campaign.* | A workflow connecting CRM preparation with a deliberate campaign send.           |
| Welcome flow           | *Add new subscribers to our Brevo list and send a welcome email after they confirm their signup.*                                      | Contact capture and a message at the chosen point in the signup flow.            |
| Appointment reminders  | *Build a booking app that sends an SMS reminder the day before an appointment.*                                                        | A reminder schedule and message delivery through your enabled Brevo SMS account. |
| Internal notifications | *Email the operations team through Brevo when an order needs manual review.*                                                           | An alert containing the order details and a link to the review screen.           |
| Newsletter signup      | *Create a newsletter signup page with consent fields and an admin view for preparing product announcements.*                           | Subscriber collection and a campaign preparation interface.                      |

A recurring sequence or a scheduled reminder must be built into the workflow you request. Saving a Brevo connection does not start a campaign or turn on an automatic schedule.

## Connect Brevo to Mythos

You need a Brevo account, its REST API key, and permission to create connections in your Mythos workspace. Use an existing saved connection if your team has already shared the correct Brevo account with you.

Before building a sending feature, prepare the sender for that channel in Brevo. Email, SMS, and WhatsApp sends use your Brevo allowance or credits and require the channel's approved sender. Brevo handles its own billing, account approval, and usage limits.

### 1. Get your Brevo API key

1. Sign in to Brevo and open **SMTP & API → API keys**.
2. Generate a new API key and name it for this connection, such as `Mythos messages`.
3. Copy the key and store it securely.

Use a REST API key, not an SMTP password. Paste it into Mythos's **API key** field, not a chat message or a public file. Brevo's [API documentation](https://developers.brevo.com/docs/getting-started) links to its authentication and sender setup guides.

### 2. Save the connection

1. From the Dashboard, open **Connectors** and select **Brevo**. If no saved connection is available, the setup form opens.
2. Enter a **Display name**, such as `Customer messaging`.
3. Paste the key into **API key**.
4. Under **Sharing**, the connection starts as **Private**. Choose **Share with others** for selected members, or **Share with workspace** for the whole workspace.
5. Click **Connect Brevo**. Mythos checks the key against your account before saving it. The connection check does not send a message.

To use it in an app, open **Chat actions (+) → Project connectors** in that project. Select the saved Brevo connection and click **Use in this project**. Then ask Mythos to build your sending or contact-management flow.

For a first feature, keep the outcome specific:

> Add a signup form for our newsletter. Save subscribers to the Product updates list in Brevo, record their consent, and show a confirmation after the contact is saved.

For a sending feature, also provide the intended sender and describe the message. Use an inbox or phone number you control when checking the resulting flow before directing messages to customers.

## Limits and delivery problems

The connector cannot enable a messaging channel or replenish its credits. If email, SMS, or WhatsApp sending is refused, check the account's available credits, channel status, sender approval, and recipient details in Brevo. A valid API key does not guarantee that every channel is ready to send.

You can read supported statistics and message events to build a status view. Connecting Brevo does not automatically deliver incoming webhooks to your app, and webhook management is not available through this connector. Configure any separate webhook integration in Brevo.

The connection also does not provide a different Brevo login for every person using your app. All actions use the account behind the saved key. If customers can view contact or campaign data, tell Mythos which records each customer is allowed to access.

If requests fail after previously working, check whether the key was revoked or replaced in Brevo. For a temporary usage-limit response, review the request frequency instead of repeatedly attempting the same operation. See the [Brevo API reference](https://developers.brevo.com/reference) for the provider's error details.

## Manage your connection

Open **Connectors → Brevo**, then your saved connection. Use **Linked projects → Unlink projects** to remove access from selected projects. **Disconnect** stops Mythos from using this connection; it does not remove your contacts, campaigns, or account from Brevo.

If you change the API key, disconnect the old connection and connect Brevo again with the new key. Link it to the intended projects, ask Mythos to set up the Brevo features again, and publish the change. Features using the disconnected connection stop working until they are set up again.