Skip to content

Brevo

When to use this guide: Read this before configuring Brevo with OutboundSync to confirm what the integration covers today.

OutboundSync connects Brevo to HubSpot and Salesforce as a one-way sync for transactional email activity. Brevo webhook events are received by OutboundSync and written to the matching CRM record as structured outbound activity.

What this integration does

Section titled “What this integration does”

Brevo sends compact transactional webhook payloads, so OutboundSync uses the email address in the payload as the primary lead identifier. Campaign, template, event, timestamp, and delivery metadata are preserved where Brevo includes them.

This integration is useful when Brevo is part of your outbound or lifecycle email stack and you need sends, opens, clicks, bounces, and unsubscribes visible in CRM reporting.

What syncs into your CRM

Section titled “What syncs into your CRM”
  • Email sends and delivery requests
  • Opens and unique opens
  • Link clicks
  • Hard bounces and soft bounces
  • Unsubscribe events
  • Message, campaign, template, tag, and timestamp metadata when available

Where it syncs

Section titled “Where it syncs”
  • HubSpot — direct integration
  • Salesforce — direct integration

Combo-specific landing pages and field mappings for Brevo are not yet published. Use this page for the current support scope.

Scope and current limitations

Section titled “Scope and current limitations”
  • One-way sync. Data flows Brevo -> CRM. Updates in HubSpot or Salesforce are not written back to Brevo.
  • Email channel only. Social, phone, and inbox-management events are out of scope.
  • Limited contact enrichment. Brevo webhook payloads identify the recipient primarily by email address, so first name, last name, company, phone, and social profile fields may not be available.
  • Guided setup. Setup is currently handled with the OutboundSync team during onboarding.

Get help and next steps

Section titled “Get help and next steps”