Brevo (Sendinblue) Email & SMS Connector

Name: Brevo (Sendinblue) Email & SMS Connector
Brand: ECOSIRE
SKU: brevo-connector

核心功能

Brevo REST v3 API integration with an encrypted, company-scoped API key stored in a dedicated settings model (never hardcoded, never in source control)

Outbound email routing so Odoo Email Marketing mailings dispatch through Brevo's transactional and campaign endpoints instead of Odoo's own SMTP

SMS marketing sending through the Brevo SMS API, mapped to Odoo's native SMS Marketing and sms.sms records

Two-way contact list synchronization between res.partner / mailing.contact and Brevo contacts and lists, with configurable attribute and field mapping

Incremental sync via a scheduled ir.cron job that pushes only changed records and reconciles deletions and unsubscribes

Transactional email routing for order confirmations, invoices, portal and password-reset mails through Brevo for consistent deliverability

Campaign engagement sync — delivered, opened, clicked, bounced, and unsubscribed events flow back into Odoo mailing.trace and campaign statistics

SMS delivery-status tracking (sent, delivered, failed) written back to the originating Odoo SMS records

Brevo webhook controller endpoint that ingests real-time events with signature validation, deduplication, and a retry queue for failed deliveries

Template mapping layer that links Brevo transactional templates to Odoo mail templates so marketing keeps its Brevo-designed layouts

@api.depends computed sync-state and last-synced-timestamp fields with a clear per-record status badge in the UI

Multi-company isolation via record rules so each res.company uses its own Brevo API key, sender identities, and lists

Configuration dashboard (XML/OWL views) showing connection health, sync counts, quota usage, and recent event feed

Bounce and unsubscribe handling that suppresses future sends and updates Odoo opt-out state to protect sender reputation

Automated actions to auto-add or auto-remove contacts from Brevo lists based on Odoo tags, stages, or segments

QWeb delivery-reconciliation report comparing Brevo-reported outcomes against Odoo's expected sends for auditability

Structured error logging with human-readable messages surfaced in the Odoo UI, plus alerting on API-key or quota failures

Rate-limit-aware batching and backoff so large mailings respect Brevo API limits without dropping recipients

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Odoo 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Your team already trusts Brevo (formerly Sendinblue) for high-deliverability email and SMS — but Odoo's Email Marketing, SMS Marketing, and transactional mail still leave through Odoo's own outgoing servers, so your sender reputation, warmed-up IPs, and Brevo analytics never come into play. This build-to-order connector closes that gap. ECOSIRE designs, builds, installs, and supports a custom Odoo module that makes Brevo the delivery engine for your outbound email and SMS while keeping Odoo the system of record.

This is NOT an instant apps.odoo.com download. ECOSIRE builds this module net-new for your database, tuned to your Brevo account, sender domains, list structure, and Odoo edition. Typical delivery is 2 to 4 weeks depending on scope.

Under the hood, the module adds an authenticated integration layer against the Brevo REST v3 API using a stored API key (encrypted at rest, never committed to source). A res.company-scoped settings model holds the API key, default sender identities, and list mappings; email and SMS are dispatched over Brevo's transactional and campaign endpoints. Contact synchronization is two-way: an Odoo model derived from res.partner and mailing.contact maps to Brevo contacts and lists, with @api.depends computed fields tracking sync state and last-synced timestamps. Engagement events (delivered, opened, clicked, hard/soft bounce, unsubscribe, SMS delivery status) flow back into Odoo through Brevo webhooks handled by a controller route, updating your mailing.trace records and Odoo's native campaign statistics so your marketing dashboards reflect reality.

Everything is delivered as clean, upgrade-safe Odoo code: a proper __manifest__.py declaring dependencies (mass_mailing, sms, contacts), models under models/, access control via ir.model.access.csv plus record rules for multi-company isolation, XML/OWL views for the configuration screens and sync dashboards, automated actions and scheduled ir.cron jobs for incremental sync and retry queues, and QWeb reporting for a Brevo-vs-Odoo delivery reconciliation summary. The same codebase supports Odoo 17, 18, and 19 on both Community and Enterprise, with version-specific branches where the API surface differs.

You get the source, the configuration, documentation, a training session, and a post-launch support window — plus ECOSIRE on call to extend it as your Brevo usage grows.

你得到什么

Complete, commented Odoo module source (models, views, controllers, security, cron, QWeb reports) delivered as a versioned Git repository or ZIP

Installation and configuration on your Odoo 17, 18, or 19 database — Community or Enterprise — including Brevo API-key wiring, sender-identity setup, and list mappings

Field- and list-mapping configuration tailored to your res.partner / mailing.contact structure and Brevo attributes

Brevo webhook configuration and endpoint hardening (signature validation, HTTPS, deduplication) verified end to end

Administrator and end-user documentation covering setup, sync behavior, template mapping, troubleshooting, and reconciliation reports

A live training session for your marketing and admin team, with a recording and a quick-reference runbook

A defined post-launch support and bug-fix window (typically 30 days, extendable) with a clear SLA

Odoo version-compatibility notes and an upgrade path so the module moves cleanly across 17 to 18 to 19

这是给谁的

Marketing Manager on Brevo

Runs email and SMS campaigns and already relies on Brevo's warmed IPs, deliverability, and analytics. Wants to launch mailings from Odoo where the CRM and segments live, but keep Brevo as the delivery engine and single source of engagement truth.

Odoo Administrator / IT Lead

Owns the Odoo instance and its integrations. Needs a clean, upgrade-safe module with proper access control, multi-company isolation, encrypted credentials, and reliable cron-based sync — not a brittle script that breaks on the next Odoo upgrade.

Revenue / Operations Lead

Cares that transactional emails (invoices, confirmations, portal notices) actually land and that campaign performance is measurable. Wants unified reporting where Odoo campaign stats reflect Brevo's real delivery, open, click, and bounce data.

Brevo (Sendinblue) Email & SMS Connector 如何比较

标准	伊科西尔	定制建造	竞争对手
Sends Odoo email & SMS through Brevo's deliverability engine	包含	部分支持	部分支持
Two-way contact & list sync (res.partner / mailing.contact ↔ Brevo)	包含	部分支持	部分支持
Engagement events fed back into Odoo mailing.trace & campaign stats	包含	部分支持	不包括在内
Built for your exact Brevo account, senders, lists & Odoo edition	包含	包含	不包括在内
Upgrade-safe across Odoo 17, 18 & 19 with a maintained port path	包含	部分支持	部分支持
Multi-company isolation via record rules (per-company keys & lists)	包含	部分支持	不包括在内
Documentation, team training & post-launch support window	包含	不包括在内	部分支持
Full source ownership, no vendor lock-in	包含	包含	不包括在内

关于Brevo (Sendinblue) Email & SMS Connector的常见问题

How long until the connector is live in our Odoo?

This is a build-to-order module, not an instant download — ECOSIRE builds it net-new for your database. Typical delivery is 2 to 4 weeks from the time we confirm scope and receive Brevo API access. Simple single-company setups land nearer 2 weeks; multi-company, custom template mapping, or heavy field-mapping work pushes toward 4. We share a milestone plan up front and give you a staging build to review before go-live.

What support and updates come with it, and after?

Every build includes a post-launch support window (typically 30 days) covering bug fixes and configuration help under a defined SLA. You also receive the full source, so nothing is locked in. After the window, we offer optional support-and-maintenance retainers that keep the module current with Brevo API changes and with new Odoo releases — we support 17, 18, and 19 and will port your build forward when you upgrade.

Do we need Odoo Enterprise, or does Community work?

Both work. The connector builds on Odoo's Email Marketing (mass_mailing) and SMS (sms) modules, which exist in Community and Enterprise alike. We tailor the build to your edition — where an API or view differs between Community and Enterprise or across versions 17/18/19, we branch the code accordingly so you get a clean, upgrade-safe result on your exact stack.

Is it two-way sync, and how are contacts kept aligned?

Yes. Contacts sync in both directions between Odoo (res.partner / mailing.contact) and Brevo contacts and lists. A scheduled ir.cron job runs incremental sync — pushing only changed records — while Brevo webhooks feed unsubscribes, bounces, and list changes back into Odoo in near real time. You configure exactly which fields and lists map, and each record shows a computed sync-state badge and last-synced timestamp.

Will campaign and delivery analytics show up inside Odoo?

Yes. Brevo webhooks push delivered, opened, clicked, bounced, and unsubscribed events into Odoo, updating mailing.trace records and the native campaign statistics so your Odoo dashboards reflect Brevo's real outcomes. We also ship a QWeb reconciliation report comparing Brevo-reported delivery against Odoo's expected sends, so you can audit any gap between the two systems.

How are our Brevo API keys and data kept secure?

The Brevo API key is stored in a company-scoped settings model, encrypted at rest, and never committed to source control. Webhook endpoints validate signatures and deduplicate events. Access to the connector's models and settings is governed by ir.model.access.csv and record rules, including per-company isolation so a multi-company database keeps each company's keys, senders, and lists separate. All Brevo traffic uses HTTPS.