Send email from n8n with Brevo

Use the native Brevo node in n8n to send transactional emails and manage contacts as part of a workflow.
View as Markdown

Overview

n8n ships with a built-in Brevo node (and a Brevo Trigger node) authenticated with a Brevo API key — no custom HTTP requests needed for supported operations, including sending email and managing contacts.

Prerequisites

  • An n8n instance (Cloud or self-hosted)
  • A Brevo account

Send email from an n8n workflow

1

Create a Brevo API key

  1. In Brevo, click Settings (gear icon) in the left sidebar, then open SMTP & API > API keys & MCP (direct link: app.brevo.com/settings/keys/api).
  2. Click + Generate API key, name it (e.g. n8n), and copy it.

Create a dedicated key for n8n rather than reusing one from another integration, so you can revoke it independently later.

2

Add Brevo credentials in n8n

  1. In your n8n workflow, add a Brevo node.
  2. Under Credential, click Create New Credential.
  3. Paste your Brevo API key and save. n8n tests the connection automatically.
3

Configure the node to send an email

  1. In the node’s action list, actions are grouped by category (Contact Actions, Contact Attribute Actions, Email Actions, etc.) rather than a two-step Resource/Operation picker.
  2. Under Email Actions, choose Send a transactional email.
  3. Fill in the sender, recipient(s), subject, and content fields. (If you need to send from a saved Brevo template instead, check the node’s action list for a template-based email action — this wasn’t directly confirmed against a live n8n workspace.)
4

Connect a trigger

Connect the Brevo node to whatever should start the send — a Webhook node, a Brevo Trigger node (for events coming from Brevo itself), a schedule, or another app’s node (e.g. a form submission or CRM update).

5

Test the workflow

Run the workflow manually (or trigger it end-to-end) and confirm delivery in Brevo > Transactional > Email logs.

Going further

If you need an operation the Brevo node doesn’t expose, use the HTTP Request node instead: choose Authentication > Predefined Credential Type, select Brevo, and pick your saved credential to call any Brevo API endpoint directly.

Troubleshooting

  • Credential test fails: confirm the API key was copied in full and hasn’t been revoked in Brevo.
  • Email not received: check that the sender is verified in Brevo, and review the node’s output for an error response.
  • Rate limit errors: check your Brevo plan’s sending limits if you’re running high-volume workflows.