Add Contact to List: Brevo action

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
List ID list_id	string	Required	List ID. Example: 2
Email Addresses emails	array	Required	List of contact emails to add to the list. Each email is a separate entry — do NOT comma-separate them inside one value.

Sample request

{
  "list_id": "e.g. 2",
  "emails": "[\"john@example.com\", \"jane@example.com\"]"
}

Returns

{
  "contacts": {
    "failure": [],
    "success": [
      "john@example.com"
    ]
  }
}

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

FAQ

Questions about Add Contact to List.

What does the Add Contact to List action do in Brevo?

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.

What inputs does Add Contact to List require?

Required: List ID, Email Addresses. 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 Add Contact to List support batch operations?

Yes. Run Add Contact to List inside a Loop node to process arrays. Tiny Command handles Brevo's rate limits automatically so you don't have to throttle manually.

More actions