Create Lead
hunter.create_lead
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Save a new lead with POST /leads. The address is the identity: Hunter refuses one that is already on the team, so use this for genuinely new people and Update Lead for the rest.
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
17 fields, 1 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 |
|---|---|---|---|---|---|
email The lead's email address — the value Hunter deduplicates on. | string | Yes | — | email format | — |
first_name The lead's first name. | string | No | — | — | Ada |
last_name The lead's last name. | string | No | — | — | — |
position The lead's job title at the company. | string | No | — | — | — |
company The company the lead works for. | string | No | — | — | — |
company_industry The company's industry. | string | No | — | — | — |
company_size The company's headcount band, as Hunter stores it. | string | No | — | — | — |
confidence_score Hunter's confidence in the address, 0 to 100 — carry over the score from the search that produced this lead. | number | No | — | 0–100 | — |
website The company website URL. | string | No | — | url format | — |
country_code The lead's country as a two-letter ISO 3166-1 alpha-2 code, for example 'FR'. | string | No | — | 2–2 characters | — |
linkedin_url The lead's LinkedIn profile URL. | string | No | — | url format | — |
phone_number The lead's phone number. | string | No | — | — | — |
twitter The lead's X/Twitter handle. | string | No | — | — | — |
notes Free-text notes stored on the lead. | string | No | — | — | — |
source Where the lead came from, for your own reporting. | string | No | — | — | — |
leads_list_id Id of the leads list to file the lead under. | string | No | — | — | — |
extra Any further lead attributes as JSON, including custom_attributes, sent through to the API untouched. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"first_name": "Ada"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Hunter's id for the saved lead. | number | — |
email The lead's email address. | string | — |
first_name The lead's first name, when Hunter has one. | string | — |
last_name The lead's last name, when Hunter has one. | string | — |
position The lead's job title, when Hunter has one. | string | — |
company The company the lead works for, when Hunter has one. | string | — |
confidence_score Hunter's confidence in the address, 0 to 100. | number | — |
leads_list The leads list the lead belongs to. | object | — |
{
"company": "",
"confidence_score": 0,
"email": "",
"first_name": "",
"id": 0,
"last_name": "",
"leads_list": {},
"position": ""
}See Create 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.