Update Contact

brevo.update_contact
ActionEmailconnection required

Calls the Brevo API with the connection's credentials.

Update an existing contact's attributes, external id or list membership. Pass EMAIL inside 'attributes' to change the address itself.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Brevo
Secret shape
the API key, or {"api_key": "…"}
Config it needs
sender_email, sender_name, sms_sender
Resolved by
config.connection_id, else node.connection_id

Configuration

8 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
identifier
The contact to address — its email address by default, or the id, phone number or ext_id named by 'identifier_type'.
stringYes——jane@example.com
identifier_type
How Brevo should read 'identifier'. Leave blank to let Brevo infer it from the value.
stringNo—one of "email_id", "phone_id", "contact_id", "ext_id", "whatsapp_id", "landline_number_id"—
attributes
Attributes to set, keyed by the attribute name in capitals, e.g. {"LASTNAME": "Roger"}.
objectNo—≥ 1 characters{"LASTNAME":"Roger"}
list_ids
Numeric ids of lists to subscribe the contact to.
arrayNo—≥ 1 characters; array of string["12"]
unlink_list_ids
Numeric ids of lists to unsubscribe the contact from.
arrayNo—≥ 1 characters; array of string["7"]
ext_id
New external id to store on the contact.
stringNo———
email_blacklisted
Set or clear the contact's email unsubscribe flag.
booleanNo———
sms_blacklisted
Set or clear the contact's SMS unsubscribe flag.
booleanNo———
  • At least one of attributes, list_ids, unlink_list_ids, ext_id, email_blacklisted, sms_blacklisted must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "attributes": {
    "LASTNAME": "Roger"
  },
  "identifier": "jane@example.com",
  "list_ids": [
    "12"
  ],
  "unlink_list_ids": [
    "7"
  ]
}

Output

One shape.

result

FieldTypeExample
updated
True when Brevo accepted the update.
boolean—
identifier
The contact that was updated.
string—
{
  "identifier": "",
  "updated": false
}

See Update Contact run in a workflow.

In a technical demo we add the Brevo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.