List Contact Lists

emelia.list_lists
ActionEmailconnection required

Calls the Emelia API with the connection's credentials.

List the contact lists on the account, with their contact counters.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
page
Which page of lists to return; Emelia starts at page 1.
numberNo—≥ 1—
limit
How many lists to return per page; Emelia returns 25 by default.
numberNo—≥ 1—
search
Return only lists whose name contains this text.
stringNo———
lead_search
Return only the lists that contain this exact email or LinkedIn URL.
stringNo——jane@example.com
status
Return only lists in this status, as Emelia spells it.
stringNo———
sort_by
Column the lists are sorted by.
stringNo—one of "name", "leads", "emails", "phones", "createdAt"—
sort_dir
Direction the rows are sorted in when a sort column is named.
stringNo—one of "asc", "desc"—

Example configuration

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

{
  "lead_search": "jane@example.com"
}

Output

One shape.

result

FieldTypeExample
items
The lists Emelia returned for this page.
array—
count
How many lists this page carried.
number—
total
How many lists match in total.
number—
page
The page number Emelia returned, when it paged.
number—
page_size
How many rows per page Emelia used.
number—
total_leads
How many contacts the matching lists hold.
number—
{
  "count": 0,
  "items": [],
  "page": 0,
  "page_size": 0,
  "total": 0,
  "total_leads": 0
}

See List Contact Lists run in a workflow.

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