Update Lead

hunter.update_lead
ActionCRM & salesconnection required

Calls the Hunter API with the connection's credentials.

Change a saved lead with PUT /leads/{id}. Only the fields you fill in are sent; everything else keeps its stored value. The API acknowledges with 204 and no body.

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

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

FieldTypeRequiredDefaultConstraintsExample
lead_id
Hunter's id for the lead to change.
stringYes———
email
A new email address for the lead. Leave blank to keep the stored one.
stringNo—email format—
first_name
The lead's first name.
stringNo——Ada
last_name
The lead's last name.
stringNo———
position
The lead's job title at the company.
stringNo———
company
The company the lead works for.
stringNo———
company_industry
The company's industry.
stringNo———
company_size
The company's headcount band, as Hunter stores it.
stringNo———
confidence_score
Hunter's confidence in the address, 0 to 100 — carry over the score from the search that produced this lead.
numberNo—0–100—
website
The company website URL.
stringNo—url format—
country_code
The lead's country as a two-letter ISO 3166-1 alpha-2 code, for example 'FR'.
stringNo—2–2 characters—
linkedin_url
The lead's LinkedIn profile URL.
stringNo—url format—
phone_number
The lead's phone number.
stringNo———
twitter
The lead's X/Twitter handle.
stringNo———
notes
Free-text notes stored on the lead.
stringNo———
source
Where the lead came from, for your own reporting.
stringNo———
leads_list_id
Id of the leads list to file the lead under.
stringNo———
extra
Any further lead attributes as JSON, including custom_attributes, sent through to the API untouched.
objectNo———
  • At least one of first_name, email, last_name, position, company, company_industry, company_size, confidence_score, website, country_code, linkedin_url, phone_number, twitter, notes, source, leads_list_id, extra must be set.

Example configuration

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

{
  "first_name": "Ada"
}

Output

One shape.

result

FieldTypeExample
updated
True once Hunter accepted the change.
boolean—
id
The lead id that was changed.
string—
lead
The lead object when Hunter returned one; empty on the documented 204 no-content answer.
object—
{
  "id": "",
  "lead": {},
  "updated": false
}

See Update Lead 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.