Brevo n8n integrationAutomate Brevo with n8n.

Adds a contact to Brevo and returns the record that was just created. Nothing is marked required on this operation, so an empty call still goes through and leaves you with a contact that has no address attached.

• Email: the contact address, in the name@email.com shape the field suggests, usually {{ $json.email }} when the address comes from a form or an earlier node.
• Contact Attributes: the array of attributes added along with the contact, one name and one value per entry.

Looks for the address first, then creates the contact or updates the existing one. This is the operation that stops a list from filling with near duplicates when the same person submits two forms.

• Email: required here, unlike on Create. It identifies the contact, so an empty value blocks the execution of the node instead of writing an anonymous record.
• Contact Attributes: the array of attributes to update, applied whether the contact was created or already existed.

Removes the contact from Brevo. There is no soft delete and no undo, so this belongs at the end of a branch that has already decided, not in the middle of a cleanup run.

• Contact Identifier: the email in urlencoded form, the numeric ID of the contact, or the value of its SMS attribute. Any of the three works, which is handy when the deletion request arrives with a phone number rather than an address.

Reads one contact and returns its attributes, which makes it the usual second node after a trigger that only hands over an address.

• Contact Identifier: required. Accepts the urlencoded email, the contact ID or its SMS attribute value, commonly written as an expression such as {{ $json.email }} so the value follows the item through the workflow.

Pulls a batch of contacts out of Brevo, one item per contact, for exports and audits rather than for single lookups.

• Return All: on, n8n walks the API pages until every contact is back. Off, Limit caps how many come through.
• Filters: narrows the set before it reaches the canvas.
• Sort: orders results by record creation, ascending or descending.
• Modified Since: keeps only contacts modified after a UTC date-time, urlencoded, in YYYY-MM-DDTHH:mm:ss.SSSZ format.

Changes attribute values on a contact that already exists, and fails rather than creating one if the identifier matches nothing. That strictness is the point: use it when the record must be there.

• Contact Identifier: required. The urlencoded email, the contact ID or the SMS attribute value.
• Attributes: the array of attributes to update, each with its name and its new value.

Declares a new contact attribute in the account, which is the field the contact operations will later fill. Four values are required, more than on any other operation of the node.

• Category: required, one of normal, transactional, calculated, category or global.
• Name: required, the attribute name.
• Type: required, text, date, float or boolean.
• Value: required, the value of the attribute.

Edits an attribute that already exists in the account. The interesting detail sits in the categories: only three of the five are offered here, so a normal or transactional attribute cannot be reshaped this way.

• Category: calculated, category or global.
• Name: the name of the existing attribute, which has to match exactly.
• Value: the value to update.
• Contact Attributes: under Update Fields, the list of values and labels the attribute can take.

Drops an attribute from the contact model. Every contact loses that field, so it is worth exporting first and deleting second.

• Category: which family the attribute belongs to, among normal, transactional, calculated, category and global. The five categories are all available here, unlike on the update operation.
• Name: the attribute to remove.

Lists the attributes declared in the account, which is how a workflow checks what exists before trying to write into it.

• Return All: on, every attribute comes back across as many API pages as needed. Off, Limit sets the maximum number returned.

Sends a transactional email composed inside the node, so the content lives in the workflow rather than in Brevo.

• Sender and Receipients: both required, and an empty one stops the execution.
• Send HTML: switches the body between Text Content and HTML Content.
• Subject: the subject line.
• Receipients CC and Receipients BCC: extra recipients, under Additional Fields.
• Email Tags: labels a message for later retrieval, next to Attachments in the same collection.

Uses a template designed in Brevo instead of HTML typed into n8n, which keeps the layout with the people who own the brand.

• Receipients: required, the only field the node insists on.
• Template ID: a dropdown fed by the account, so there is no ID to memorize.
• Template Parameters: under Additional Fields, the set of attributes that customize the template, typically expressions like {{ $json.order_id }}.
• Attachments and Email Tags: files to join and labels for retrieval.

Registers a sender in the account, the identity transactional emails will go out under. Both fields are required, which makes this the simplest operation of the node to get right.

• Name: required, the display name recipients see next to the address.
• Email: required, the sender address, in the name@email.com shape.

Removes a sender from the account. Anything still pointing at that identity has to be updated first, since the send operations name a sender explicitly.

• Sender ID: the ID of the sender to delete, not its address. Get Many Senders is the usual way to find that ID, often chained as {{ $json.id }} straight into this field.

Returns the senders available in the account, with their IDs, which is what makes the delete operation practical.

• Return All: on, the node pages through the API until the full list is back. Off, Limit caps the number of senders returned.