This trigger is initiated by a web-hook created in Brevo and this field will be used for the web-hook's description, displayed in the Brevo user interface.

By default this trigger returns only event data and contact's email address. If you need all contact data then set this to True.

The email address of the contact to be added/updated. If not provided, then Mobile Number must be provided instead.

The mobile number of the contact to be added/updated. Format should like 91xxXxxXxxXx, +91xxXxxXxxXx, or 0091xxXxxXxxXx.  If not provided, then Email must be provided instead. If both are provided and the contact exists, then the contact will be identified by one of them and the other will be updated.

Select the list(s) to which contact will be added.

The new contact will be added to the list(s) selected above. In case _Add_ an existing Brevo contact will remain in all list(s) that he was already in and he will be added to the list(s) selected above, in case _Reassign_ an existing Brevo contact will be removed from all list(s) he was in and he will be added to the list(s) selected above.

(Deprecated - Please use upper fields for direct attributes mapping. If the same attribute is maped in upper fileds and here this one will overwrite the upper one.) Map your attributes. In the first row, type the name of your Brevo attribute in uppercase (Attributes have to be created in your Brevo account beforehand). In the second row, map their values with the fields from the output of your trigger. If you map the date type of attribute value, be sure to modify date to format "YYYY-MM-DD" by using Zapier Formatter step (`https://zapier.com/help/create/format/modify-date-formats-in-zaps`). For boolean type attributes, you can use "true" or "false" as string, 0 or 1 as numbers or real Boolean values. For category type attributes there is the option to use category name or category ID - it can be selected in next field.

Brevo contact's attributes which have type `category` could be supplied by either value or ID. If category IDs are supplied for attribute values, then this option should be set to True.

The email address of contact that is added.

Select the list(s) to which your contact will be added.

_Add_ - an existing Brevo contact will remain in all list(s) that they were already in and be added to the list(s) selected above.
_Reassign_ - an existing Brevo contact will be removed from all list(s) they were in and be added to the list(s) selected above.

Map your attributes. In the left column, type the name of your Brevo attribute in uppercase (Attributes have to be created in your Brevo account beforehand). In the right column, map them with the attributes of your trigger app. If you map the date type of attribute value, be sure to modify date to format "YYYY-MM-DD" by using Zapier Formatter step (`https://zapier.com/help/create/format/modify-date-formats-in-zaps`). For Brevo SMS field, the expected format is +33xxxxxxxxx). For boolean type attributes, you can use "true" or "false" as string, 0 or 1 as numbers or real Boolean values.

The email address of the contact to be found. If not provided, then Mobile Number must be provided instead.

The mobile number of the contact to be found. Format should like 91xxXxxXxxXx, +91xxXxxXxxXx, or 0091xxXxxXxxXx. If not provided, then Email must be provided instead.

Who will this email be sent to? You can add multiple email addresses.

Who should be cc'd on this email? You can add multiple email addresses.

Who should be bcc'd on this email? You can add multiple email addresses.

Name of the sender from which the emails will be sent.

Email of the sender from which the emails will be sent.

HTML body of the message (Mandatory if 'Text Content' is not passed).

Plain Text body of the message (Mandatory if 'HTML Content' is not passed. Note that 'Text Content' will be ignored if 'HTML Content' is passed).

Enter an absolute URL or select a value from a previous step in your Zap to pass the absolute URL of your attachment (it cannot be a local file). For example, `https://attachment.domain.com/myAttachmentFromUrl.jpg`. Format allowed: xlsx, xls, ods, docx, docm, doc, csv, pdf, txt, gif, jpg, jpeg, png, tif, tiff, rtf, bmp, cgm, css, shtml, html, htm, zip, xml, ppt, pptx, tar, ez, ics, mobi, msg, pub, eps and odt.

File attachments. Select form previous step "File (exists but not shown). The overall size of email with all attachments should not be more then 5 Mb."

Tag your emails to find them more easily.

The email address of the existing Brevo contact that will be unsubscribed.

Select the list(s) from which your contact should be unsubscribed.

API docs for Brevo are located here https://apidocs.sendinblue.com/

Requests can only be made to domains associated by this application. View [documentation](https://help.zapier.com/hc/en-us/articles/12899607716493) for more details.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses grow.

Zapier Automation Platform

PRODUCTS

CAPABILITIES

By use case

By app

By team

By company size

How Zapier Zaps

How Zapier Uses AI

By team

Learn more

Get help

Zapier quick-start guide

Developer resources

Brevo Integrations

Brevo Help & Support

How to Get Started with Brevo (formerly SendinBlue) on Zapier

Brevo Tutorials

5 ways to automate Brevo (formerly Sendinblue) with Zapier

About Brevo

Related categories