Sending outbound webhooks from an automation allows you to send a real-time notification with event data from Brevo to an external app when a contact reaches the Call a webhook step.
This article explains how to send outbound webhooks from an automation. You can also create outbound webhooks by configuring them directly in your Brevo account or from the API.
Before you start
From your external app, make sure to retrieve the URL of the server or endpoint you want to send the outbound webhook to. If you're unsure where to retrieve it, check your external app's help center or contact their support team.
Send outbound webhooks from an automation
To send outbound webhooks from an automation, you need to add the Call a webhook step and configure it with your webhook URL and authentication details.
Use the following tabs to view instructions for the new or classic automation editor:
- In an automation created using the new editor, add a Call a webhook step.
- Enter the URL of the server or endpoint you want to send your events to. This tells Brevo where to send the outbound webhook when an event happens.
- Select an Authentication method from the dropdown:
- No authentication: The webhook will be sent without authentication credentials.
- Basic: Enter your username and password. Brevo will encode these credentials and send them with each webhook request.
- Token: Enter your authentication token. Brevo will send this token with each webhook request.
-
(Optional) Click Add object to add custom headers to your webhook request. Enter the header name and value. You can add multiple headers if needed.
💡 Good to knowCustom headers are useful for authentication or passing additional metadata to your external app. - (Optional) Under the Additional settings section, configure what data is included in the webhook:
- Include details of the contact who triggered the event: When activated, Brevo includes all contact attributes for the contact in the webhook. By default, only the contact ID, email, step ID, and workflow ID are included.
- Include details of the trigger event: When activated, Brevo includes the event data from the payload in the webhook.
- Click Save to save the step.
- Finish setting up your automation and activate it.
- From an automation created using the classic editor, add an entry point.
- (Optional) Add the steps you want your contacts to go through before triggering the webhook.
- Add the Call a webhook step to your automation:
- On the canvas, click + where you want to add the Call a webhook step.
- Select the Call a webhook step.
-
Paste the webhook URL provided by your external app. This callback URL tells Brevo where to send data when an event happens.
💡 Good to knowThe webhook URL must be generated and retrieved from your external app. If you're unsure where to retrieve it, check your external app's help center or contact their support team. - (Optional) Activate the I want to send contact properties to the webhook option to include contact properties in the webhook.
- Click OK.
- Finish setting up your automation and activate it.
Secure your outbound webhooks
To secure your outbound webhooks, whitelist some of Brevo's IP ranges. This ensures that only authorized requests can trigger webhooks.
➡️ To learn more, check our dedicated article Brevo IP ranges: List of publicly exposed services.
⏭️ What's next?
- Create outbound webhooks to send real-time data from Brevo to an external app
- Create inbound webhooks to receive real-time data from another app in Brevo
🤔 Have a question?
If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.
If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo Agency partner.