List Leads

hunter.list_leads
ActionCRM & salesconnection required

Calls the Hunter API with the connection's credentials.

Return one page of saved leads with GET /leads, filtered by list, address or company, or by any other filter key the API documents.

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

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

FieldTypeRequiredDefaultConstraintsExample
leads_list_id
Only return leads filed under this list.
stringNo———
email
Only return the lead with this exact address.
stringNo—email format—
company
Only return leads at this company.
stringNo———
limit
How many leads to return in this page, 1 to 1000. Hunter returns 20 when you leave it blank.
numberNo—1–1000—
offset
How many results to skip before the page starts, for paging through a large domain.
numberNo—0–100000—
filters
Any further query parameters as JSON, for example {"country_code": "FR"}, sent through untouched.
objectNo——{"country_code":"FR"}

Example configuration

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

{
  "filters": {
    "country_code": "FR"
  }
}

Output

One shape.

result

FieldTypeExample
items
The leads in this page.
array—
count
How many leads this page contains.
number—
total
How many leads match the filter 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 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.