Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Brevo connector page.How webhooks are set up
No configuration is required in Brevo. When you connect your account, StackOne creates the webhook subscriptions for you and removes them again when you disconnect.
Two subscriptions are created
Brevo separates webhooks by type, so StackOne registers two — one Transactional webhook and one Marketing webhook — both pointing at the same StackOne callback URL. They appear in Brevo under Settings > Webhooks, on the corresponding tabs, with the description StackOne managed webhook (transactional/marketing).
Do not edit or delete them in Brevo
These subscriptions are managed by StackOne. Editing or deleting them in the Brevo interface stops event delivery until the account is reconnected.
Check your webhook allowance
Brevo allows a maximum of 40 webhooks per account, across marketing and transactional combined. If your account is at the limit, delete unused webhooks in Brevo before connecting.
How events are delivered
Points to be aware of when consuming Brevo events.
Some events arrive from both subscriptions
Delivery, open, click, bounce, spam and unsubscribe activity is reported by both the transactional and the marketing webhook. Marketing deliveries carry campaign identifiers in the payload, which distinguishes them from transactional ones.
Contact events can be high volume
Contact Updated fires on every attribute change, including bulk imports and list synchronisations, so it can generate significant traffic on large accounts.
Only new activity is delivered
Events are sent from the moment the connection is made. Brevo does not replay activity that occurred beforehand.
Retries on failure
Brevo retries a failed delivery up to four times, after 10 minutes, 1 hour, 2 hours and 8 hours. A 4xx response other than 429, or any 5xx response, stops retries and the event is discarded.
Available webhook events
The events below can be enabled for this connection.
Transactional email events
Fired for emails sent through the Brevo transactional API or SMTP relay.
- Email Sent (
request) — Fired when Brevo accepts the send request. - Email Delivered (
delivered) — Fired when the email reaches the recipient’s server. - Email Opened (
opened) — Fired each time a recipient opens the email. - Email Unique Opened (
unique_opened) — Fired on a recipient’s first open only. - Email Clicked (
click) — Fired when a recipient clicks a tracked link. - Email Soft Bounced (
soft_bounce) — Fired on a temporary delivery failure. - Email Hard Bounced (
hard_bounce) — Fired on a permanent delivery failure. - Invalid Email (
invalid_email) — Fired when the recipient address is not valid. - Email Deferred (
deferred) — Fired when delivery is temporarily delayed. - Spam Complaint (
complaint) — Fired when a recipient marks the email as spam. - Email Unsubscribed (
unsubscribed) — Fired when a recipient unsubscribes. - Email Blocked (
blocked) — Fired when Brevo blocks the email from being sent.
Marketing campaign events
Fired for emails sent as part of a marketing campaign.
- Marketing Hard Bounce (
hardBounce) — Fired on a permanent campaign delivery failure. - Marketing Soft Bounce (
softBounce) — Fired on a temporary campaign delivery failure. - Marketing Spam Report (
spam) — Fired when a recipient reports a campaign as spam.
Contact events
Fired for contacts in your Brevo account.
- Contact Created (
list_addition) — Fired when a contact is added to one or more lists. - Contact Updated (
contact_updated) — Fired when a contact’s details change. - Contact Deleted (
contact_deleted) — Fired when a contact is removed.