Short answer: Drop the "Brevo → Update Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email or Contact ID identifier | string | Required | The email address or numeric ID of the contact to update |
First Name first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
SMS Phone sms | string | Optional | Phone number in E.164 format |
Add to List IDs list_ids | string | Optional | Comma-separated list IDs to add the contact to |
Remove from List IDs unlink_list_ids | string | Optional | Comma-separated list IDs to remove the contact from |
{"identifier": "user@example.com","first_name": "e.g. Jane","last_name": "e.g. Doe","sms": "+15551234567","list_ids": "e.g. 2,5"}
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.