Start free
ActionBrevoUpdated June 2026

How do I update a Brevo contact?

Short answer: You can update contact in Brevo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Brevo Update Contact action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 9 Brevo actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Email or Contact ID
identifier
stringRequiredThe email address or numeric ID of the contact to update
First Name
first_name
stringOptionalContact's first (given) name.
Last Name
last_name
stringOptionalContact's last (family) name.
SMS Phone
sms
stringOptionalPhone number in E.164 format
Add to List IDs
list_ids
stringOptionalComma-separated list IDs to add the contact to
Remove from List IDs
unlink_list_ids
stringOptionalComma-separated list IDs to remove the contact from
Sample request
{
  "identifier": "user@example.com",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe",
  "sms": "+15551234567",
  "list_ids": "e.g. 2,5"
}
Returns
{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Update Contact.

Any of these apps can fire this action as part of a workflow.

Gmail → Brevo
1 Gmail triggers
Slack → Brevo
13 Slack triggers
Google Sheets → Brevo
2 Google Sheets triggers
HubSpot → Brevo
18 HubSpot triggers
FAQ

Questions about Update Contact.

What does the Update Contact action do in Brevo?
Partial update on a contact's attributes and list memberships. Only passed fields change. For "enriched from external source → write back" or "plan tier changed → update Brevo for segment accuracy" sync patterns.
What inputs does Update Contact require?
Required: Email or Contact ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Brevo returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update Contact support batch operations?
Yes. Run Update Contact inside a Loop node to process arrays. TinyCommand handles Brevo's rate limits automatically so you don't have to throttle manually.
More actions

Other Brevo actions.

Action
Add Contact to List
Adds an existing contact to a specific Brevo list. If the contact isn't in the account, this fails — use Create Contact first or the upsert pattern. List membership drives campaign targeting.
Action
Create Contact
Creates or upserts (when updateEnabled=true) a contact with email, attributes, and initial list memberships. The base hook for "form submission → push to Brevo" sync workflows.
Action
Delete Contact
Hard-deletes the contact and history. Irreversible — for GDPR right-to-erasure compliance workflows. For soft removal that preserves engagement history, unsubscribe or move to a suppression list instead.
Action
Get Contact
Returns the contact by email or ID with all attributes and list memberships. The standard lookup for enrichment workflows or for resolving "is this email in Brevo already" before downstream decisions.
Action
List Contacts
Paginated contacts with filters by list, segment, modified date. For sync workflows that mirror Brevo into a warehouse, paginate with the modifiedSince filter to incrementally pull only touched records.
Action
List Brevo Lists
Returns every list in the connected account with name, contact count, folder. Useful for populating list-pickers at workflow setup or for inventorying audience structure.