Update Leads List
hunter.update_leads_list
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Rename an existing lead list with PUT /leads-lists/{id}.
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, 2 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 |
|---|---|---|---|---|---|
leads_list_id Hunter's id for the list to rename. | string | Yes | — | — | — |
name The new name for the list. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
updated True once Hunter accepted the change. | boolean | — |
id The list id that was renamed. | string | — |
leads_list The list object when Hunter returned one; empty when it answered with no content. | object | — |
{
"id": "",
"leads_list": {},
"updated": false
}See Update Leads List 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.