DEV Community

Alfaz Mahmud Rizve
Alfaz Mahmud Rizve

Posted on Edited on

The email stack I actually run: Brevo for n8n + transactional mail

Every n8n workflow I run ends in an inbox somewhere. This is the tool that sends it.

I run Brevo every day. It is the email layer under my n8n work: transactional mail, CRM contacts, and lists, all driven by API from the workflows themselves.

That is the whole review in one sentence, but the reason it matters is the part people skip. Email is not the hard part of outbound. Deliverability is. And Brevo is a tool that makes you do the deliverability work properly, instead of pretending it does not exist.

What it does in my stack

Apollo finds the prospect. n8n moves the record. Brevo holds the contact and sends the mail.

The connection is the API, not the dashboard. My n8n workflows push contacts into Brevo with an upsert pattern — same contact in twice does not create a duplicate — and enrol them in lists by ID. The credential is a header auth key, and the calls are plain HTTP requests from n8n. Nothing in the chain depends on a browser session or a manual export.

That shape is why Brevo fits an automation stack. A tool that only works when a human clicks through its UI is a dead end for n8n work. Brevo's API is the product here, and the dashboard is where you check the results.

I also use it for transactional mail — the receipts, alerts, and confirmations that workflows send when something happens. Same account, same API, different job from the outreach lists. Keeping both in one place means one sender reputation to watch instead of two.

What worked

API-first, for real. Contact upserts, list enrolment, and sending all work over the API with clear success codes. My pipeline draft targets a 99.8% success rate on upserts, and the failures that do happen are visible in the response, not silent.

One place for mail and CRM. The contact, the list, and the send live in the same system. When a workflow updates a contact's job title or headcount, that change is in the record the next send uses. No sync job between two tools to break.

The warming discipline is written down. Brevo does not warm your IP for you, and it should not — warming is a schedule, not a switch. My SOP for it covers the setup that actually decides whether mail lands: SPF, DKIM, and DMARC records, a gradual volume climb, and n8n throttling so a workflow cannot blast a cold IP on day one. The full guide is here: https://whoisalfaz.me/blog/brevo-cold-email-ip-warming-guide/

What broke — or rather, what is hard

Nothing about Brevo broke. The hard part is the part no vendor can fix for you: a cold IP has no reputation, and inbox providers treat unknown senders as guilty until proven otherwise.

Three honest limits:

  1. Warming takes weeks. Volume climbs on a schedule. If you need to send 10,000 emails on day one, Brevo will not save you — no tool will. The schedule in the SOP is the price of a working sender reputation.
  2. A shared IP borrows reputation. Start on shared sending and your deliverability rides with other senders. A dedicated IP is the fix, and it is the thing that needs warming.
  3. List hygiene is your job. Bad addresses and stale contacts hurt the sender score, and Brevo will not stop you from mailing them. The dedup and domain checks in my pipeline exist because dirty data costs reputation.

None of that is a reason not to use it. It is a reason to use it the way it is built to be used: API-driven, warmed slowly, lists kept clean.

Who it is for

Brevo fits if you run outbound or transactional mail from n8n and you are willing to do the warming work. It fits agencies that want mail and CRM in one API-driven place.

It does not fit if you want zero-setup bulk sending with no DNS records and no schedule. That buyer will be unhappy with any honest tool, Brevo included.

The deal, plainly

Brevo's programme pays €100 per paid account and €5 per free signup, after the first paid referral. If you try it through my link, that is the arrangement: https://whoisalfaz.me/go/brevo

The pipeline that connects Apollo to Brevo through n8n — webhooks, dedup, CRM sync, the copy-pasteable workflow — is written up here: https://whoisalfaz.me/blog/apollo-brevo-n8n-outbound-pipeline/

And if your Brevo mail rides on n8n schedules, check the 3.0 guide before December. The Cron node your workflows use today is gone in 3.0: https://whoisalfaz.me/blog/how-to-upgrade-to-n8n-3-without-breaking-workflows/

Brevo is the email stack I actually run. Not because it is magic, but because it is honest about the work — and the work is the whole game.


Alfaz Mahmud Rizve — GTM & RevOps Architect. I build autonomous revenue systems for scaling agencies and SaaS: SEO & organic growth, high-speed Next.js apps, and self-healing n8n workflows. whoisalfaz.me

Top comments (0)