Email Verifier
hunter.email_verifier
ActionCRM & salesconnection required
Calls the Hunter API with the connection's credentials.
Check whether one address is deliverable with GET /email-verifier, returning the MX, SMTP and disposable-domain checks behind the verdict rather than a bare yes or no.
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
1 field, 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 email address to verify. | string | Yes | — | email format | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status The verdict: valid, invalid, accept_all, webmail, disposable or unknown. | string | — |
email The address that was checked. | string | — |
score Deliverability confidence, 0 to 100. | number | — |
regexp The address has a valid format. | boolean | — |
gibberish The local part looks machine-generated. | boolean | — |
disposable The domain is a throwaway-mailbox service. | boolean | — |
webmail The domain is a webmail provider such as Gmail. | boolean | — |
mx_records The domain publishes MX records. | boolean | — |
smtp_server The mail server accepted a connection. | boolean | — |
smtp_check The mailbox itself was accepted by the server. | boolean | — |
accept_all The server accepts every address, so a valid result proves little. | boolean | — |
block The server blocked the verification attempt. | boolean | — |
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 | — |
{
"accept_all": false,
"block": false,
"disposable": false,
"email": "",
"gibberish": false,
"meta": {},
"mx_records": false,
"regexp": false,
"score": 0,
"smtp_check": false,
"smtp_server": false,
"sources": [],
"status": "",
"webmail": false
}Notes
- Hunter answers 202 while a check is still running; the status you get back is then not final, so re-run the node to poll for it.
- An accept_all domain answers 'accept_all', not 'valid' — treat it as unproven rather than as a failure.
See Email Verifier 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.