Add Contacts To List

brevo.add_contacts_to_list
ActionEmailconnection required

Calls the Brevo API with the connection's credentials.

Subscribe existing contacts to a list, addressing them by email, numeric id or ext_id. Only one of the three may be used per call.

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

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

FieldTypeRequiredDefaultConstraintsExample
list_id
Numeric id of the Brevo contact list to act on.
stringYes——12
emails
Email addresses of existing contacts, at most 150 per call.
arrayNo—≥ 1 characters; array of string["jane@example.com"]
ids
Numeric contact ids, at most 150 per call.
arrayNo—≥ 1 characters; array of string["42"]
ext_ids
EXT_ID attribute values of existing contacts, at most 150 per call.
arrayNo—≥ 1 characters; array of string["crm-8891"]
  • At least one of emails, ids, ext_ids must be set.

Example configuration

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

{
  "emails": [
    "jane@example.com"
  ],
  "ext_ids": [
    "crm-8891"
  ],
  "ids": [
    "42"
  ],
  "list_id": "12"
}

Output

One shape.

result

FieldTypeExample
list_id
The list the contacts were added to or removed from.
string—
success
Identifiers Brevo applied the change to.
array—
failure
Identifiers Brevo refused, e.g. already in or out of the list.
array—
process_id
Background job id, set only when removing every contact.
number—
total
Contacts the background removal covers, when one was started.
number—
{
  "failure": [],
  "list_id": "",
  "process_id": 0,
  "success": [],
  "total": 0
}

Notes

  • Brevo caps this at 150 contacts per call; import larger batches through its /contacts/import endpoint instead.

See Add Contacts To List 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.