List Leads Lists
hunter.list_leads_lists
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Return the lead lists on the team with GET /leads-lists.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Hunter
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
limit How many lists to return in this page, 1 to 1000. Hunter returns 20 when you leave it blank. | number | No | — | 1–1000 | — |
offset How many results to skip before the page starts, for paging through a large domain. | number | No | — | 0–100000 | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The lead lists in this page. | array | — |
count How many lists this page contains. | number | — |
total How many lists the team has in total, as Hunter reports it in the meta envelope; the page count when it reports none. | number | — |
meta Hunter's 'meta' envelope: the parameters it echoed back and, for a search, the total number of results. | object | — |
{
"count": 0,
"items": [],
"meta": {},
"total": 0
}See List Leads Lists run in a workflow.
In a technical demo we add the Hunter connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.