ActionBrevoUpdated September 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.

Update Contact in Brevo — start free All 9 Brevo actions

Update Contact in Brevo — start free

Inputs

The fields this action accepts.

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

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.

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 run history shows the failed step with its input and the error message Brevo returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Contact support batch operations?

Run Update Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Brevo's rate limits.

More actions