> 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/faq.md).

# 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](/sources/category/email/brevo/data-overview.md). If you're running into connection or missing data problems, check [Common Issues](/sources/category/email/brevo/common-issues.md). For tips on structuring your data flows effectively, see [Best Practices](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.