Marketing

Brevo AI automation and integrations

The short answer

Brevo, formerly Sendinblue, is easy to automate. Its v3 API uses a single API key, it sends webhooks for both marketing and transactional events, and n8n has a built-in Brevo node and trigger, with Zapier and Make apps too. Because Brevo handles marketing email, SMS and transactional email in one account, it suits AI workflows that send personalized onboarding, follow-up and notification messages from your own systems.

What you can automate with Brevo

Onboarding emails from product events

Send each new customer an onboarding message written from their signup data and first actions, through Brevo transactional email.

Read the build guide
Sales follow-up sequences

Enroll new leads in follow-up sequences by intent and stop them automatically when a reply or booking comes in.

Read the build guide
Newsletter drafted from your content

Gather new posts and updates, draft a newsletter in your voice and create it as a draft campaign for approval.

Read the build guide
Event registration and reminders

Add registrants to lists with attributes and send confirmation, reminder and follow-up emails and SMS.

Read the build guide
Appointment reminders by SMS and email

Send reminders from your booking system and handle replies such as confirm or reschedule.

Read the build guide
Contact sync with your CRM or store

Keep contacts, attributes and list membership aligned with your CRM or ecommerce data, with unsubscribes flowing back.

Read the build guide

What makes Brevo easy to automate

Brevo bundles marketing email, SMS, WhatsApp campaigns, transactional email, a basic CRM and live chat in one account. For automation that is convenient. One API key and one API can update a contact, send a personalized transactional email and add the contact to a campaign list.

The v3 API is consistent and well documented. Authentication is a single API key in a header, which is easy to set up in any tool. Webhooks are available for transactional events (delivered, opened, clicked, bounced) and marketing events (unsubscribed, list additions and more). n8n has a Brevo node and trigger, and Zapier and Make both have Brevo apps, so most workflows need no custom code.

The AI layer

Brevo includes AI help for writing campaigns. Where custom AI adds real value is in event-driven messages built from your own data:

  • Onboarding. A customer signs up and takes a few actions. A model writes a short, specific next-step email based on what they did, and Brevo sends it as transactional mail. Our onboarding email guide covers the safeguards.
  • Follow-up. Leads get follow-ups that reference their form answers or the page they came from, and sequences stop the moment someone replies.
  • Reminders. Appointment reminders over SMS and email with simple reply handling reduce no-shows for service businesses. See AI appointment reminders.

We constrain the model to a short section inside a tested template. Links, legal text and unsubscribe handling stay fixed.

Limits to plan around

  • Attributes first. Contact attributes must be created in Brevo before you can write them. A sync that invents new fields will fail until someone adds them.
  • Rate limits by endpoint. Transactional sending and contact endpoints have different limits that depend on plan. Batch contact imports instead of looping.
  • Sender and domain setup. Authenticate your sending domain (SPF, DKIM, DMARC) before automating anything, or messages land in spam regardless of content.
  • SMS rules. SMS consent and quiet-hours rules are strict. Keep consent flags accurate and send only to contacts who opted in.
  • API key scope. API keys are account-wide. Create one per integration and restrict authorized IPs where your hosting allows it, so a leaked key can be revoked without breaking everything else.

How Lumeor typically connects it

A typical build uses n8n with a webhook from your app or CRM. The workflow loads the contact and recent activity, asks a model for a short personalized section with a strict length limit, inserts it into a Brevo transactional template and sends. The Brevo Trigger feeds bounces and unsubscribes back to the CRM. For newsletters we create draft campaigns that a person approves.

A single workflow typically sits in our workflow automation range. Book a call to scope yours.

Frequently asked questions

Is Brevo the same as Sendinblue?

Yes. Sendinblue renamed itself Brevo in 2023. Older tutorials and some integrations still use the Sendinblue name, and the v3 API carried over, so most existing integrations kept working after the rename.

Does n8n work with Brevo?

Yes. n8n has a built-in Brevo node for contacts, contact attributes, transactional email and senders, and a Brevo Trigger that receives webhook events. Other endpoints, such as campaigns or SMS, are reachable with the HTTP Request node and the same API key.

Should AI-generated emails go through marketing campaigns or transactional email?

It depends on the message. One-to-one messages triggered by something the person did, such as signing up or booking, fit transactional sending. Messages to a list, like newsletters, belong in campaigns where unsubscribe handling and consent rules apply. Do not route marketing content through transactional sending to avoid opt-outs.

Does Brevo have its own AI features?

Brevo includes AI tools for writing campaign content and subject lines inside the product. Use them for one-off campaigns. Custom AI is useful when messages must be generated from your own data automatically, at the moment an event happens.

Next steps