> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/email/brevo.md).

# Brevo

Connect Brevo to Coupler.io to sync contacts, segments, campaign stats, and CRM deals into Google Sheets or data warehouses automatically.

Brevo (formerly Sendinblue) is an all-in-one marketing platform covering email campaigns, SMS, CRM, and contact management. Connecting Brevo to Coupler.io lets you pull your campaign stats, contact lists, CRM deals, and more into any destination you choose — no manual exports needed.

**Why connect Brevo to Coupler.io?**

* Sync contacts, segments, and lists into Google Sheets or a data warehouse for deeper audience analysis
* Combine email and SMS campaign performance data in one dashboard
* Export CRM deals, tasks, and pipeline stages to track sales activity alongside marketing metrics
* Send Brevo data to AI destinations like ChatGPT, Claude, or Gemini to surface insights from your campaigns

## Prerequisites

* A Brevo account (any plan)
* A Brevo API key — you can generate one from **Brevo → Account → SMTP & API → API Keys**

## Quick start

{% hint style="success" %}
Start with the **Contacts** or **Email Campaigns** entity — these tend to be the most immediately useful for reporting.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Go to your Coupler.io workspace and click **Add data flow**. Search for and select **Brevo** as the source.
{% endstep %}

{% step %}
**Enter your Brevo API key.** In the source settings, paste your API key into the API Key field. You can find or generate your key in Brevo under **Account settings → SMTP & API → API Keys**.
{% endstep %}

{% step %}
**Choose an entity.** Select the data entity you want to export — for example, Contacts, Email Campaigns, or CRM Deals. You can add more entities to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to specify how far back you want data pulled from.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data sent — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync and confirm your data is flowing correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                     | Description                                  |
| -------------------------- | -------------------------------------------- |
| Contacts                   | All contacts in your Brevo account           |
| Contacts attributes        | Custom and default contact field definitions |
| Contacts folders           | Folder structure for organizing lists        |
| Contacts folders lists     | Lists within each folder                     |
| Contacts lists             | All contact lists                            |
| Contacts lists contacts    | Contacts belonging to a specific list        |
| Contacts segments          | Saved audience segments                      |
| Senders                    | Configured sender addresses                  |
| Companies                  | CRM company records                          |
| Companies attributes       | Custom fields defined for companies          |
| CRM pipeline stages        | Stages in your CRM pipeline                  |
| CRM pipeline details all   | Full pipeline configuration details          |
| CRM attributes deals       | Custom fields for deals                      |
| CRM deals                  | All deals in your CRM                        |
| CRM task types             | Task type definitions                        |
| CRM tasks                  | Tasks in your CRM                            |
| CRM notes                  | Notes attached to CRM records                |
| Domains                    | Sending domains configured in your account   |
| Webhooks                   | Webhook configurations                       |
| Accounts                   | Account-level information                    |
| Organization invited users | Users invited to your organization           |
| Email campaigns            | Email campaign records and stats             |
| SMS campaigns              | SMS campaign records and stats               |

## Brevo data overview

Brevo exposes a broad range of data across contact management, CRM, and campaign channels. Below is a breakdown of what's available through each entity.

## Entity summary

| Entity                     | What it contains                                                      |
| -------------------------- | --------------------------------------------------------------------- |
| Contacts                   | Email, subscription status, creation date, custom attributes          |
| Contacts attributes        | Field names, types, and categories for contact properties             |
| Contacts folders           | Folder IDs and names                                                  |
| Contacts folders lists     | Lists nested inside folders                                           |
| Contacts lists             | List names, IDs, subscriber counts                                    |
| Contacts lists contacts    | Contacts mapped to a specific list                                    |
| Contacts segments          | Segment rules, names, and IDs                                         |
| Senders                    | Sender name, email, and verification status                           |
| Companies                  | Company name, domain, linked contacts                                 |
| Companies attributes       | Custom field definitions for companies                                |
| CRM pipeline stages        | Stage name, order, and pipeline ID                                    |
| CRM pipeline details all   | Full pipeline metadata                                                |
| CRM attributes deals       | Custom deal field definitions                                         |
| CRM deals                  | Deal name, value, stage, owner, dates                                 |
| CRM task types             | Task category labels                                                  |
| CRM tasks                  | Task title, due date, status, linked contact or deal                  |
| CRM notes                  | Note content, creation date, linked record                            |
| Domains                    | Domain name, verification and authentication status                   |
| Webhooks                   | URL, event triggers, creation date                                    |
| Accounts                   | Plan type, credits, account email                                     |
| Organization invited users | Invitee email, role, and invitation status                            |
| Email campaigns            | Campaign name, status, send date, open rate, click rate, unsubscribes |
| SMS campaigns              | Campaign name, status, send date, delivered, unsubscribes             |

#### Email campaign metrics

| Metric        | Description                                      |
| ------------- | ------------------------------------------------ |
| Unique opens  | Number of unique recipients who opened the email |
| Total opens   | Total open events including repeat opens         |
| Clicks        | Total clicks on links in the email               |
| Unique clicks | Number of unique clickers                        |
| Unsubscribes  | Recipients who unsubscribed after this campaign  |
| Bounces       | Hard and soft bounces                            |
| Spam reports  | Recipients who marked as spam                    |
| Delivered     | Emails successfully delivered                    |
| Sent          | Total emails sent                                |

#### Email campaign dimensions

| Dimension           | Description                        |
| ------------------- | ---------------------------------- |
| Campaign ID         | Unique identifier for the campaign |
| Campaign name       | Name as set in Brevo               |
| Subject line        | Email subject                      |
| Status              | Draft, queued, sent, or archived   |
| Send date           | Scheduled or actual send timestamp |
| Sender name / email | The sender identity used           |

#### SMS campaign metrics

| Metric       | Description                     |
| ------------ | ------------------------------- |
| Delivered    | Messages successfully delivered |
| Sent         | Total messages sent             |
| Unsubscribes | Recipients who opted out        |

#### Contact dimensions

| Dimension              | Description                                  |
| ---------------------- | -------------------------------------------- |
| Email                  | Contact email address                        |
| SMS                    | Contact phone number (if captured)           |
| First name / Last name | Name fields                                  |
| Created at             | Date contact was added                       |
| Modified at            | Date contact was last updated                |
| Email blacklisted      | Whether the contact is globally unsubscribed |
| SMS blacklisted        | Whether the contact has opted out of SMS     |
| Custom attributes      | Any fields you've defined in Brevo           |

#### CRM deal dimensions

| Dimension       | Description                       |
| --------------- | --------------------------------- |
| Deal name       | Name of the deal                  |
| Amount          | Deal value                        |
| Stage           | Current pipeline stage            |
| Owner           | Assigned user                     |
| Close date      | Expected or actual close date     |
| Linked contacts | Contacts associated with the deal |

## Common metric combinations

* **Email campaigns + Contacts lists** — Join on list ID to see which audience segments are driving the best open rates
* **CRM deals + CRM tasks** — Combine to get a full activity picture per deal, including pending follow-ups
* **Contacts + Email campaigns** — Use Append to merge contact attributes with campaign engagement for segmentation analysis
* **Email campaigns + SMS campaigns** — Append both entities to compare cross-channel performance in one report

## Use cases by role

{% tabs %}
{% tab title="Marketers" %}

* Pull email and SMS campaign stats into Google Sheets or Looker Studio to build a unified campaign performance dashboard
* Export contacts and segments to analyze audience growth over time
* Send campaign data to ChatGPT or Claude to generate performance summaries or subject line recommendations
* Use Append transformation to combine email and SMS campaign results in one table
  {% endtab %}

{% tab title="CRM & Sales teams" %}

* Export CRM deals and pipeline stages into a spreadsheet to track deal velocity and stage distribution
* Join CRM tasks with deals to see activity levels per opportunity
* Pull CRM notes into a data warehouse for historical activity logging
* Use Aggregate transformation to summarize deal values by owner or pipeline stage
  {% endtab %}

{% tab title="Operations" %}

* Monitor organization invited users to audit team access
* Export webhooks and domains for infrastructure documentation
* Pull account data to track plan usage and credit consumption
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Brevo uses API key authentication — there is no OAuth flow. Keep your API key secure and rotate it if shared accidentally.
* Contact custom attributes are defined per account — export **Contacts attributes** alongside **Contacts** to understand what each field means.
* The **Contacts lists contacts** entity requires selecting a specific list — add multiple sources in one data flow to pull contacts from several lists at once.
* Campaign statistics in Brevo are updated in near real-time after a send, but some metrics like unsubscribes may have a short delay.
* SMS campaigns have fewer available metrics than email campaigns by design.

## Brevo common issues

### Connection issues

<details>

<summary>Invalid API key error when connecting</summary>

Double-check that you've copied the full API key from Brevo — it's easy to accidentally trim characters. Go to **Brevo → Account settings → SMTP & API → API Keys** and regenerate the key if needed, then paste the new one into Coupler.io.

</details>

<details>

<summary>Data flow connects but returns no data</summary>

Make sure the entity you selected actually contains data in your Brevo account. For example, if you pick **CRM deals** but haven't created any deals, the export will be empty. Check the relevant section in Brevo directly.

</details>

### Missing data

<details>

<summary>Historical campaign data is missing or incomplete</summary>

Brevo's API limits how far back some data is accessible depending on your plan. Check your Brevo plan's data retention limits. Also make sure you've set an appropriate start date using the date picker in the data flow settings — if the start date is too recent, older records will be excluded.

</details>

<details>

<summary>Contact custom attributes are showing as empty columns</summary>

Custom attribute values are only populated if contacts have those fields filled in. Export the **Contacts attributes** entity to see which fields are defined, then cross-reference with your Contacts export. Attributes that have never been set will appear blank.

</details>

<details>

<summary>Contacts lists contacts entity returns no rows</summary>

This entity pulls contacts for a specific list. If the list you selected is empty in Brevo, the export will return nothing. Verify the list has subscribers in Brevo's Contacts section before re-running.

</details>

### Permission errors

<details>

<summary>403 Forbidden error on specific entities</summary>

Some Brevo entities — particularly CRM features — are only available on certain plans. If you get a 403 on CRM deals, pipeline stages, or tasks, check whether your Brevo subscription includes CRM access. Upgrading your plan or switching to a plan that includes those features will resolve the error.

</details>

<details>

<summary>API key doesn't have access to all features</summary>

Brevo lets you create restricted API keys scoped to specific features. If your key was created with limited permissions, certain entities will fail. Generate a new key with full access or expand the permissions on your existing key in Brevo's API key settings.

</details>

### Data discrepancies

<details>

<summary>Campaign stats in Coupler.io don't match what I see in Brevo</summary>

Brevo updates some metrics (especially opens and clicks) in near real-time, so there can be a small lag between what Brevo's dashboard shows and what the API returns at the time of your sync. Re-run your data flow a few hours after a campaign send for the most settled numbers.

</details>

### Rate limits

<details>

<summary>Sync fails with a rate limit or 429 error</summary>

Brevo's API enforces rate limits that vary by plan. If you're pulling a large number of entities in one data flow or running syncs very frequently, you may hit these limits. Try reducing the number of entities in a single run or spacing out your scheduled syncs.

</details>

## Brevo FAQ

<details>

<summary>Where do I find my Brevo API key?</summary>

Log into Brevo and go to **Account settings → SMTP & API → API Keys**. Click **Generate a new API key**, give it a name, and copy the key. Paste it into the API Key field in Coupler.io when setting up your data flow.

</details>

<details>

<summary>Can I connect multiple Brevo accounts to Coupler.io?</summary>

Yes. Each Brevo account has its own API key. Add a separate source connection in Coupler.io for each account using the respective API key. You can then use the Append transformation to combine data from multiple accounts into one output.

</details>

<details>

<summary>Can I pull data from multiple contact lists in one data flow?</summary>

Yes. Add the **Contacts lists contacts** entity as multiple sources within the same data flow — one per list — and use the Append transformation to merge them into a single table.

</details>

<details>

<summary>Why does my CRM deals export not show stage names — only IDs?</summary>

Brevo's CRM deals entity returns a stage ID rather than the stage name. Add **CRM pipeline stages** as a second source in the same data flow and use the Join transformation on the stage ID field to enrich your deals data with readable stage names.

</details>

<details>

<summary>What's the difference between Contacts folders, Contacts folders lists, and Contacts lists?</summary>

* **Contacts folders** — the top-level folder structure you've created in Brevo to organize lists
* **Contacts folders lists** — the individual lists sitting inside each folder
* **Contacts lists** — all lists in your account regardless of folder, including total subscriber counts

Use all three together if you want a full picture of your audience organization.

</details>

<details>

<summary>Can I send Brevo campaign data to an AI tool for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. Select one as your destination when setting up the data flow, and your Brevo campaign data will be sent there for analysis, summarization, or content generation.

</details>

<details>

<summary>Does Coupler.io support Brevo transactional email data?</summary>

The current Brevo source in Coupler.io covers marketing campaigns (email and SMS), contacts, and CRM data. Transactional email logs are not available as a separate entity at this time.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

Use the date picker in the data flow's source settings to set a start date. How far back data is available depends on your Brevo plan's data retention policy — check your Brevo plan details for specifics.

</details>

{% hint style="info" %}
For details on what fields are available per entity, see [Data Overview](#brevo-data-overview). If you're running into connection or missing data problems, check [Common Issues](#brevo-common-issues). For tips on structuring your data flows effectively, see [Best Practices](https://docs.coupler.io/sources/category/email/brevo/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/email/brevo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
