List Contact Lists

brevo.list_lists
ActionEmailconnection required

Calls the Brevo API with the connection's credentials.

Fetch the contact lists in the account, newest first by default.

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

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

FieldTypeRequiredDefaultConstraintsExample
limit
How many lists to return in one page.
numberNo101–50—
offset
Index of the first list of the page, for paging.
numberNo0≥ 0—
sort
Order the page by creation date, ascending or descending.
stringNo—one of "asc", "desc"—

Example configuration

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

{
  "limit": 10,
  "offset": 0
}

Output

One shape.

result

FieldTypeExample
items
The lists on this page, with their subscriber counts.
array—
count
Total contact lists in the account.
number—
returned
How many lists this page actually carries.
number—
{
  "count": 0,
  "items": [],
  "returned": 0
}

See List Contact Lists 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.