Connect Brevo to FastHook
Connect Brevo contacts, lists, and email events to FastHook Workflows. Manage subscribers and send transactional emails.
Choose from 24 Triggers and 11 Actions.
Connect your account
Connect with a Brevo API v3 key from SMTP & API → API Keys. FastHook validates the key and stores it encrypted.
- In Brevo, open SMTP & API → API Keys and create a key for FastHook.
- In FastHook Sources, choose New source → Provider app → Brevo. Connect your account with that key.
- Choose a contact or email event and save the Source. FastHook creates the webhook automatically.
- Add Brevo Actions to a Workflow, map contact attributes and list IDs, test the Workflow, then activate it.
Example automations
- Save form submissions as Brevo contacts and add them to a selected list.
- Notify your team when an email bounces or a contact unsubscribes.
- Send a transactional confirmation from a verified Brevo sender after a Workflow completes.
Triggers
- Marketing Spam
- Marketing Opened
- Marketing Click
- Marketing Hard Bounce
- Marketing Soft Bounce
- Marketing Unsubscribe
- Marketing List Addition
- Marketing Delivered
- Marketing Contact Updated
- Marketing Contact Deleted
- Transactional Request
- Transactional Delivered
- Transactional Hard Bounce
- Transactional Soft Bounce
- Transactional Blocked
- Transactional Spam
- Transactional Invalid Email
- Transactional Deferred
- Transactional Click
- Transactional Opened
- Transactional Unique Opened
- Transactional Unsubscribed
- Any Brevo Event
- Custom Brevo Events
Actions
- Create or Update Contact
- Get Contact
- Update Contact
- Delete Contact
- Add Contacts to List
- Remove Contacts from List
- Create List
- Get List
- Send Transactional Email
- Get Account
- Custom API Request
Working with Brevo
Brevo currently restricts OAuth apps to users inside their own organization. External FastHook customers connect with their own API v3 key.
FastHook manages separate marketing and transactional email webhooks, verifies Bearer authentication, and deduplicates repeated event deliveries.
Transactional emails require a verified sender and sufficient Brevo credits. Subscription status and consent must match your contact's preferences.
Contact attributes vary by account. Use attributes defined in Brevo, such as FIRSTNAME; list IDs are numeric JSON values.
Brevo may restrict API access by IP. If a valid key is denied, check the account's authorized IP settings.
Webhook schemas come from official examples. Optional fields vary by event; triggers retain the original event payload.
Brevo reference · Explore Brevo integrations · Brevo API documentation