Brevo Trigger

Triggers when Brevo email events occur

Overview

The Brevo Trigger node listens for webhook events from Brevo (formerly Sendinblue). It can receive transactional email events (delivered, opened, clicked, bounced, blocked, deferred, spam, unsubscribed), marketing campaign events (delivered, opened, clicked, bounced, spam, unsubscribed, list addition), and inbound email events. The node receives the raw event payload from Brevo and passes it into the workflow for processing.

Category: Marketing
Tool Name: brevo_trigger
Version: 1

Appearance: Icon: si-brevo | Color: #0092ff

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Brevo credentials. See the Credentials Guide for setup instructions.

Parameters

All Resources

Parameter	Type	Required	Default	Description
Resource (type)	options	Yes	transactional	The type of email events to listen for.
				Options: inbound, marketing, transactional

Transactional (transactional)

Parameter	Type	Required	Default	Description
Trigger On (transactionalEvents)	multiOptions	Yes	[]	Which transactional email events to listen for. (shown when Resource is transactional)
				Options: blocked (email blocked), click (email clicked), deferred (email deferred), delivered (email delivered), hardBounce (email hard bounced), invalid (email invalid), spam (email marked as spam), opened (email opened), request (email sent), softBounce (email soft bounced), uniqueOpened (email opened for the first time), unsubscribed (recipient unsubscribed)

Marketing (marketing)

Parameter	Type	Required	Default	Description
Trigger On (marketingEvents)	multiOptions	Yes	[]	Which marketing email events to listen for. (shown when Resource is marketing)
				Options: click (marketing email clicked), delivered (marketing email delivered), hardBounce (marketing email hard bounced), listAddition (a contact was added to a list), opened (marketing email opened), softBounce (marketing email soft bounced), spam (marketing email marked as spam), unsubscribed (recipient unsubscribed)

Inbound (inbound)

Parameter	Type	Required	Default	Description
Trigger On (inboundEvents)	multiOptions	Yes	[]	Which inbound email events to listen for. (shown when Resource is inbound)
				Options: inboundEmailProcessed (an inbound email was processed)

Output Data

Brevo sends one event per request, so each delivery produces one output item carrying the payload exactly as sent. Transactional and marketing events typically include event, email, id, date, ts, message-id, ts_event, subject, tag, sending_ip, ts_epoch, and template_id; inbound events carry the parsed message instead.

Three fields are added to every item:

• _trigger — always brevo_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the event Brevo reported

Reference the payload downstream by expression, e.g. {{ $json.email }} or {{ $json.event }}.

Usage Examples

• Track when transactional emails are delivered
• Monitor email open rates in real-time
• React to email bounces and unsubscribes
• Process inbound emails received by Brevo
• Trigger follow-up when marketing email links are clicked

Example Configuration

Transactional email events:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "transactional",
    "transactionalEvents": ["delivered", "opened", "click"]
  }
}

Marketing email events:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "marketing",
    "marketingEvents": ["delivered", "opened", "click", "unsubscribed"]
  }
}

Inbound email events:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "inbound",
    "inboundEvents": ["inboundEmailProcessed"]
  }
}

Every transactional event:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "transactional",
    "transactionalEvents": [
      "blocked",
      "click",
      "deferred",
      "delivered",
      "hardBounce",
      "invalid",
      "spam",
      "opened",
      "request",
      "softBounce",
      "uniqueOpened",
      "unsubscribed"
    ]
  }
}

Basic delivery tracking — sent, delivered, opened:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "transactional",
    "transactionalEvents": ["request", "delivered", "opened"]
  }
}

Campaign engagement tracking:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "marketing",
    "marketingEvents": ["opened", "click", "listAddition"]
  }
}

Deliverability monitoring:

{
  "type": "brevo_trigger",
  "parameters": {
    "type": "transactional",
    "transactionalEvents": ["hardBounce", "softBounce", "blocked", "spam"]
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Select a resource type (Transactional, Marketing, or Inbound) and choose which events to listen for. Brevo will send a POST request to the webhook URL whenever the selected events occur. The webhook must be registered with Brevo via their API. ⚠ Brevo does not sign webhooks (no HMAC). Treat the webhook URL as a secret — anyone with the URL can fire events. Do not commit it to repos or share publicly.

• One resource per node. A Brevo subscription covers a single resource type. To watch both transactional and marketing activity, add one Brevo Trigger for each and merge their outputs.
• request means “sent”, not “requested”. It is the event Brevo emits when it hands a transactional email to the recipient’s mail server.
• opened vs uniqueOpened. opened fires on every open; uniqueOpened fires only the first time a given recipient opens the message.
• Branch on the event. One subscription can carry many event types; switch on {{ $json.event }} when different events need different handling.