Email Finder
hunter.email_finder
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Find the most likely email address for one named person at one company with GET /email-finder, and return it with a confidence score and the sources behind it.
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
7 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 |
|---|---|---|---|---|---|
domain The company's domain name, for example 'stripe.com'. Give this or 'company'. | string | No | — | — | stripe.com |
company The company name, when you do not know its domain. Give this or 'domain'. | string | No | — | — | — |
first_name The person's first name. | string | No | — | — | — |
last_name The person's last name; goes with 'first_name'. | string | Conditional | — | only with first_name | — |
full_name The person's full name, as an alternative to first and last name. | string | No | — | — | Ada Lovelace |
linkedin_handle The person's LinkedIn handle, which identifies both the person and the company on its own. | string | No | — | — | — |
max_duration How long Hunter may spend looking, in seconds, 3 to 20. Longer finds more; it defaults to 10. | number | No | — | 3–20 | — |
- At least one of domain, company, linkedin_handle must be set.
- At least one of full_name, first_name, linkedin_handle must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"domain": "stripe.com",
"full_name": "Ada Lovelace"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
email The address found, or null when Hunter could not find one. | string | — |
found False when Hunter returned no address at all. | boolean | — |
score Hunter's confidence in the address, 0 to 100. | number | — |
domain The domain the address belongs to. | string | — |
first_name The person's first name, as Hunter has it. | string | — |
last_name The person's last name, as Hunter has it. | string | — |
position The person's job title, when Hunter has one. | string | — |
company The company name Hunter has for the domain. | string | — |
verification Hunter's last verification of the address: its status and the date it was checked. | object | — |
sources The public pages Hunter saw the address on. | array | — |
meta Hunter's 'meta' envelope: the parameters it echoed back and, for a search, the total number of results. | object | — |
{
"company": "",
"domain": "",
"email": "",
"first_name": "",
"found": false,
"last_name": "",
"meta": {},
"position": "",
"score": 0,
"sources": [],
"verification": {}
}See Email Finder 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.