Integrations · Marketing

Connect Brevo to Well

Attribute Brevo company record and person record to revenue in your CRM, with channel and cohort breakdown ready.

What Well pulls from Brevo

Brevo feeds company record, person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Brevo’s access.

From Brevo		In Well	Relation
Company record		Customer	Enriches
Person record		Contact	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Brevo → Well

What Well does with your Brevo connection

Connect

Connect Brevo over OAuth (MCP DCR): Well registers a client through Brevo's OAuth Dynamic Client Registration and you approve on Brevo's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings company record and person record in from Brevo through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Brevo entity into customer and contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Brevo lands in the workspace as customer and contact you can search, chart, and automate.

Questions Brevo unlocks

Ask in plain language. Well answers from your connected Brevo connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Brevo connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Brevo connection…

1 agent skill runs on Brevo.

Well lists Brevo in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Brevo

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Brevo in three steps

01
Authorise Brevo via MCP
From Well's Connections panel, search for Brevo and click Connect. Well discovers Brevo's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Brevo's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Well's MCP client discovers company record and person record from Brevo that Brevo's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Brevo records. Because Brevo ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Brevo records happens in the background.

How Brevo stays secure with Well

Well connects to Brevo's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Brevo secret. Tokens are scoped to the company record and person record Brevo exposes and refreshed server-side. Reads only, Well cannot modify or delete Brevo records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Brevo records
Resources the Brevo MCP server exposes, scoped by your OAuth approval.
granted
Resolve company record and person record across your stack
Match identifiers in Brevo against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Brevo records
Not granted; Brevo is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Brevo passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Brevo’s admin panel.

Frequently asked questions about Brevo and Well

How do I connect Brevo to Well, and how long does it take?

From Well, open Connections, find Brevo, and click Connect. Well discovers the OAuth metadata from Brevo's MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Brevo's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Brevo?

Well brings in company record, and person record from Brevo and reshapes each entity into your workspace: company record becomes customer; person record becomes contact. Every record arrives with the source identifier preserved, so Brevo stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well join Brevo audience segments to my CRM cohorts?

Brevo audience segments resolve to the workspace customer entities they target. A campaign aimed at "enterprise tier US" links to the actual enterprise-tier US customer entities in your CRM, so engagement-to-deal-stage joining happens without manual cohort matching.

Can Well surface a person record from Brevo when I ask questions in conversation?

Yes. Brevo person records are indexed in your workspace as contact, so questions like "show me last week's person records from Brevo" return them with the original Brevo link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

How often does Brevo sync with Well, and what triggers a refresh?

Well combines live Brevo events with periodic reconciliation reads of company record and person record. New rows appear within seconds when Brevo pushes them; periodic reads catch anything a push missed. The first connect backfills history from Brevo in the background.

Can I disconnect Brevo and what happens to the data Well already pulled?

Open Connections > Brevo in Well and click Disconnect. Well calls Brevo's token revocation endpoint and stops calling Brevo immediately on its side; provider-side propagation to Brevo's admin panel varies by provider. The company record and person record Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Brevo?

The Brevo records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.

Ready to connect Brevo?

Connect once. Every company record, person record from Brevo becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect BrevoTalk to us