BrevoSync - two-way contact sync and deliverability feedback

BrevoSync syncs your Dolibarr contacts and companies to Brevo based on Dolibarr categories, then feeds Brevo sending feedback back into Dolibarr. Dolibarr stays the master of business data, Brevo stays the master of campaigns and deliverability.

What goes from Dolibarr to Brevo

• Contacts and companies, using the email address as the pivot, with documented deterministic de-duplication rules.
• Configurable attribute mapping (first name, last name, company, phone) to the attributes of your own Brevo account, reloaded straight from the API.
• Dolibarr category to Brevo list mapping: only the lists declared in the mapping table are driven, a list created by hand in Brevo is never touched.
• The sync perimeter can be restricted to members of the mapped categories, so an address that no mapping designates is never created in Brevo.
• One-click immediate sync of a whole category, forced full resync, and purge of processed rows.

What comes back from Brevo into Dolibarr

• Hard bounces, spam complaints and unsubscribes, received through a webhook signed with a shared secret.
• A warning shown directly on the company and contact record, so sales people immediately know that an address no longer receives anything.
• Clean unsubscribe handling: an unsubscribe reported by Brevo is recorded in Dolibarr, or reduced to a visual warning only if you prefer.
• Counters and aggregates per feedback type, with a configurable retention period for detailed feedback.

Design principles

• A queue, not a scan. A trigger pushes the affected addresses into a queue; two scheduled jobs drain it. No sync is ever triggered by displaying a page and the database is never fully scanned.
• Unsubscribe always wins. The module never sends an implicit re-subscription: an unsubscribed contact is never silently put back on a list.
• Nothing is marked as synced without proof. Each queue row carries a lock token, an attempt counter, the last error and a retry; it only reaches the done state on a positive API response.
• No core file is modified. The module installs into htdocs/custom and can be disabled without leaving functional traces.

Setup

• Installed through the Dolibarr module manager, then enter your Brevo API v3 key, which is encrypted before storage and never displayed again.
• Four admin screens: settings, category / list mapping, sync queue, sending feedback.
• Three separate permissions: configure, synchronise, read.
• Two scheduled jobs provided and one webhook endpoint to declare in Brevo.
• Requirements: a Brevo account with an API v3 key. The Brevo free plan is enough to get started.

Compatibility

• Minimum Dolibarr version: 21.0.0 — maximum Dolibarr version: 24.0.0. Developed and tested on 23.0.3.
• PHP 7.4 to 8.4, MariaDB or MySQL.
• Module version: 2.1.0.

Licence, author and support

• GPL v3 or later, full text shipped in the COPYING file of the package. Copyright (C) 2026 Thermasse.
• Author and publisher: Thermasse (France).
• Support by email at support@thermasse.fr, in French and English, announced response time of 2 business days.
• One year of updates and bug fixes from the purchase date. Installation, training, custom development and Brevo account support are not included.
• Detailed support scope: https://www.thermasse.fr/modules/brevosync/support/

Brevo and Dolibarr are trademarks of their respective owners. BrevoSync is an independent integration module.

What's new in 2.1.1

Security and reliability release, following a code audit and an independent review. No new features.

• Hardened resilience of the contact resolver: a partial database failure can no longer result in a batch being processed on incomplete data.
• CSRF protection on every administration page.
• HTTP access restricted to the administration pages and the webhook endpoint only: scripts, SQL, documentation and language files are no longer downloadable.
• Module settings are preserved across a deactivation and reactivation.
• Migration scripts made replayable and transactional.
• Webhook secret encrypted at rest.

Please note: acknowledging a deliverability alert now requires the "Trigger Brevo synchronisation" permission instead of the read-only permission. Grant it to the users in charge of handling alerts.