Domain Search
hunter.domain_search
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Return every email address Hunter knows for a company with GET /domain-search, each with its confidence score and its sources. This is the node that spends one search credit per call.
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
8 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 | — | — | — |
limit How many addresses to return in this page, 1 to 100. Hunter returns 10 when you leave it blank. | number | No | — | 1–100 | — |
offset How many results to skip before the page starts, for paging through a large domain. | number | No | — | 0–100000 | — |
email_type Restrict the result to personal addresses or to generic ones such as contact@. Leave blank for both. | string | No | — | one of "personal", "generic" | — |
seniority Keep only people at this seniority level. Comma-separate to accept several. | string | No | — | one of "junior", "senior", "executive" | — |
department Keep only people in these departments, comma-separated, for example 'sales,marketing'. | string | No | — | — | — |
required_field Drop any address that is missing this attribute, so the page only contains rows you can act on. | string | No | — | one of "full_name", "position", "phone_number" | — |
- At least one of domain, company must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"domain": "stripe.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
domain The domain the addresses belong to. | string | — |
organization The company name Hunter has for the domain. | string | — |
pattern The address pattern Hunter inferred, for example '{first}.{last}'. Null when it could not infer one. | string | — |
emails The addresses found, each with value, type, confidence, the person's name and position, and the sources Hunter saw it on. | array | — |
count How many addresses this page contains. | number | — |
meta Hunter's 'meta' envelope: the parameters it echoed back and, for a search, the total number of results. | object | — |
{
"count": 0,
"domain": "",
"emails": [],
"meta": {},
"organization": "",
"pattern": ""
}See Domain Search 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.