- Integrations
- /
- Brevo
- /
- Triggers
- /
- Email Delivered
TriggerBrevoReal-timeUpdated May 2026
When does Brevo fire on email delivery?
Short answer: Drop the "Brevo → Email Delivered" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Brevo, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Email Delivered
When the matching event happens
watch for email deliveredwhen an email is delivered via brevonew email deliveredwhen email deliveredon email delivered
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"email": "user@example.com","event": "delivered","subject": "Hello"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| string | "user@example.com" | |
| event | string | "delivered" |
| subject | string | "Hello" |
Pairs with
Drop these actions after Email Delivered.
FAQ
Questions about Email Delivered.
How does the Email Delivered trigger work in Brevo?
Fires when the recipient mail server accepts the message. Useful for transactional confirmations ("password reset email was actually delivered, log success") and for deliverability monitoring.
Is the Email Delivered trigger real-time?
Yes. Email Delivered uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Brevo.
What data does Email Delivered return?
The full event payload from Brevo. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Email Delivered so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Brevo admin permissions to use Email Delivered?
For most Brevo accounts a standard user can authorize the trigger. Some Brevo plans require an admin to enable third-party webhooks. Check Brevo's docs if the trigger fails to register.
More triggers
Other Brevo triggers.
Trigger
Contact Updated
Fires on any change to a contact's attributes or list memberships. Payload includes the changed fields. For specific transitions (e.g., contact moved to a particular list), inspect the payload before downstream side-effects.
TriggerEmail Bounced
Fires when an outbound email bounces. Distinguishes hard vs soft in the payload. The standard hook for list-hygiene workflows: hard bounce → suppress from future sends, mark in CRM as invalid email.
TriggerEmail Clicked
Fires when a recipient clicks a tracked link in a Brevo email. Payload includes the link URL and recipient. The high-signal engagement event for behavioural workflows — click on "Book a demo" link triggers Calendly outreach automation.
TriggerEmail Opened
Fires when the recipient opens the email (tracked via the pixel). Useful for engagement-based scoring or for "warm lead — open detected, fire follow-up sequence" automations.
Build a workflow on this trigger.
One trigger. 9+ downstream actions. Zero glue.