Brevo Connector

Illustration · sample data

Sync example

Review one record

Source

Brevo

Connector status: Live

→

Destination

Your other tool

Connector status: Custom tool

Field mapping

Source field	Destination field	Sample value
record.id	source_id	record_1042
record.updated_at	updated_at	2026-10-18T08:00:00Z
record.value	value	sample_value

1. Draft
2. Review one record
3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

This connector has passed a live run. It writes contacts, lists, companies, deals, events and orders to Brevo, sends single transactional emails and SMS, and reads contacts and lists back.

What the connector does

• Creates or updates a contact by email, adds contacts to a list, and creates lists and contact attributes.
• Sets or clears a contact’s email and SMS blocklist flags, and reads Brevo’s blocked contacts with the reason.
• Creates or updates companies and CRM deals, and links contacts to companies.
• Tracks behavioural events and creates or updates e-commerce orders.
• Sends one transactional email or one transactional SMS.
• Reads contacts, filtered by when they were created or changed, and the account’s lists.
• Receives Brevo’s email event webhooks, such as delivered, opened, clicked and bounced.
• Shows a read-only report of email campaign performance.

What the live run checked

On 15 October 2026, a run against a real Brevo account created a list, upserted three test contacts, added them to the list, read them back by modification date, pulled a first page through the contacts sync and deleted everything. Nothing was sent: the email, SMS, event, company, deal and order actions were not part of that run.

Not in the connector

• WhatsApp messages
• Creating or sending email campaigns
• Loyalty programs
• Brevo Conversations (live chat)

Open-Source Implementation Map

No official open-source repository was found in the current Tajo connector catalog for Brevo. Keep this page focused on the verified public API contract and vendor documentation until an official schema, SDK, MCP server, or public integration repository is available.

Tajo Revamp Checklist

• Verify authentication and scope requirements against the vendor documentation before each connector release.
• Document primary sync objects, external IDs, pagination strategy, and rate limits explicitly.
• Add smoke tests from public API examples rather than undocumented behavior.
• Capture webhook signature verification and replay protection when the vendor supports webhooks.
• Record gaps where no official public repository or schema exists so future maintainers know what still needs source-backed validation.