Email Count
hunter.email_count
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Count the addresses Hunter holds for a domain with GET /email-count, broken down by department and seniority. The call is free, so it is the right way to size a domain before spending a search credit.
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
3 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 | — | — | — |
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" | — |
- 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 |
|---|---|---|
total How many addresses Hunter holds in total. | number | — |
personal_emails How many belong to a named person. | number | — |
generic_emails How many are role addresses such as info@. | number | — |
department The count per department. | object | — |
seniority The count per seniority level. | object | — |
meta Hunter's 'meta' envelope: the parameters it echoed back and, for a search, the total number of results. | object | — |
{
"department": {},
"generic_emails": 0,
"meta": {},
"personal_emails": 0,
"seniority": {},
"total": 0
}See Email Count 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.