Brevo
Email delivery events and contact ops from Brevo
Brevo (formerly Sendinblue) is the European-headquartered email marketing and transactional sending platform that competes with Mailchimp and SendGrid on different axes, strong on cost-effective bulk sending, friendly to teams worried about GDPR specifics. Five triggers cover delivery: Email Delivered, Email Opened, Email Clicked, Email Bounced (deliverability red flag), Contact Updated (any field change in the contact record). Nine actions cover the operational side: Send Transactional Email (using a Brevo template or raw HTML), Create Contact, Add Contact to List, Remove Contact from List, Delete Contact, Get Contact, List Contacts, List Lists. The integration uses a Brevo API key from your account settings. Common patterns: a Brevo Email Bounced fires a workflow that tags the contact as undeliverable in HubSpot and removes them from the Klaviyo audience, or Email Clicked on a high-value campaign syncs an engagement score to your CRM. Brevo's data residency in the EU makes it a natural choice for workflows where the email layer needs to stay GDPR-compliant by design.
Workflows start when Brevo does.
5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
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.
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.
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.
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.
Do anything Brevo can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Contact to List | Adds an existing contact to a specific Brevo list. If the contact isn't in the account, this fails — use Create Contact first or the upsert pattern. List membership drives campaign targeting. |
| Create Contact | Creates or upserts (when updateEnabled=true) a contact with email, attributes, and initial list memberships. The base hook for "form submission → push to Brevo" sync workflows. |
| Delete Contact | Hard-deletes the contact and history. Irreversible — for GDPR right-to-erasure compliance workflows. For soft removal that preserves engagement history, unsubscribe or move to a suppression list instead. |
| Get Contact | Returns the contact by email or ID with all attributes and list memberships. The standard lookup for enrichment workflows or for resolving "is this email in Brevo already" before downstream decisions. |
| List Contacts | Paginated contacts with filters by list, segment, modified date. For sync workflows that mirror Brevo into a warehouse, paginate with the modifiedSince filter to incrementally pull only touched records. |
| List Brevo Lists | Returns every list in the connected account with name, contact count, folder. Useful for populating list-pickers at workflow setup or for inventorying audience structure. |
| Remove Contact from List | Removes a contact from a specific list while preserving the contact record overall. Useful for "campaign ended → remove from the campaign list" lifecycle hygiene workflows. |
| Send Transactional Email | Sends a one-shot transactional email — pass either HTML body or reference a Brevo template ID with merge parameters. For "password reset, order confirmation, receipt" workflows where each email is unique to the recipient and the moment. |
| Update Contact | Partial update on a contact's attributes and list memberships. Only passed fields change. For "enriched from external source → write back" or "plan tier changed → update Brevo for segment accuracy" sync patterns. |
Pre-built Brevo workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Brevo once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Brevo field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Brevo integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Brevo to Tiny Command?
What Brevo triggers does Tiny Command support?
What Brevo actions can I run from a workflow?
Is the Brevo integration real-time?
Do I need to write code to use Brevo with Tiny Command?
How much does the Brevo integration cost?
More marketing apps people connect.
Same category as Brevo, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Brevo.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
