Resources · n8n integration

Hunter n8n integrationAutomate Hunter with n8n.

A company name is not a contact. The Hunter n8n integration turns domains and names into email addresses through 3 operations, then checks an address before anyone hits send. One API key credential, and workflows that start from a schedule, a webhook or another tool.

Try the Hunter integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Hunter n8n integration actually do?

The Hunter n8n integration wires your workflows to your Hunter account through a single node and 3 operations. Hand it a domain and it returns the email addresses found on the internet for that domain, with their sources. Hand it a domain plus a first and last name and it returns the most likely address for that person. Hand it an address and it verifies the deliverability.

Start with the case most teams hit first: a list of target companies sitting in a spreadsheet, with a website column and an empty contact column. A Google Sheets node reads the rows, the Hunter node runs Domain Search on each one with the Department filter set to sales, and the addresses go back into the sheet. The whole loop runs unattended, and the sheet stays the single place your team looks.

Second case, the opposite direction. A name arrives from a form, an event list or a scraped profile, and the company is known but the address is not. Email Finder takes the domain, the first name and the last name, and returns the most likely address, which a Pipedrive node then writes onto the person record. Nobody types an address by hand, and nobody guesses the pattern.

Third case sits right before the send. Email Verifier checks the deliverability of an address, so a workflow can branch: verified addresses go on to Gmail, the rest land in a Slack channel for a human to look at. A short If node after Hunter is all it takes to split the two paths.

The node ships with n8n on Cloud and on a self-hosted instance alike, and the credential you create once appears in the dropdown of every Hunter node afterwards. When a workflow needs an endpoint of the Hunter API that is not one of these 3 operations, the HTTP Request node calls it directly and reuses that same credential through predefined authentication, so you never paste the key twice.

One structural point to plan for: Hunter has no trigger node in n8n. A workflow around it starts with a Schedule Trigger on a fixed interval, with an n8n Webhook called by another service, or with the trigger of a different tool, and the Hunter node sits further down the chain. If you want the pattern explained end to end, the n8n review covers how these pieces fit together.

Connect

How do you connect Hunter to n8n?

  1. 01

    Generate your API key in Hunter

    Create a Hunter account first if you don't have one, then open the API keys page in your profile and generate a key. Copy that string somewhere safe for the next two minutes. It is the whole authentication method: the Hunter credential supports API key, and nothing else needs to be configured on the node.

  2. 02

    Create the credential in n8n

    Open the Credentials menu in n8n, add a Hunter credential, and paste the key into the API Key field. A credential is the stored login n8n keeps for you: you create it once and every Hunter node in every workflow picks it from a dropdown. Give it a name that matches the Hunter account it belongs to, so a second account later stays easy to tell apart.

  3. 03

    Select it on the node and run one item

    Drop a Hunter node into a workflow, choose the credential in its list, pick Email Verifier, and execute the node on one address you already know. A single required field, Email, and an answer comes back. That is the fastest way to prove the key works before you wire a sheet, a CRM and a mailbox around it.

Actions

What can the Hunter node do?

The Hunter node exposes 3 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Get every email address found on the internet using a given domain name, with sources

domainSearch

What you see in n8n

Notes & use cases

Give it a company domain and it returns the email addresses found on the internet for that domain, with their sources. The operation for when you know the company and nobody inside it.

Key parameters

  • Domain: the domain to sweep, written like stripe.com, often {{ $json.field }} when the list comes from a spreadsheet.
  • Only Emails: checked, the node returns only the found emails.
  • Return All: on, n8n pages through the API for every result; off, Limit caps how many come back.
  • Filters: optional, with Type (personal or generic), Seniority (junior, senior, executive) and Department.
Use cases
map an account before outreach by keeping the sales department at executive seniority, rather than pulling a whole domain you will never read.
02

Generate or retrieve the most likely email address from a domain name, a first name and a last name

emailFinder

What you see in n8n

Notes & use cases

Here the person is already known and the address is not. From three pieces of information, the operation returns the most likely email address for that individual.

Key parameters

  • Domain: the company domain the person works at, for example stripe.com.
  • First Name: the person's first name. Case does not matter, so a lowercase value works as it arrives.
  • Last Name: same rule, which helps when the source data shouts everything in capitals.
Use cases
fill the empty email column of a CRM export row by row, or complete a contact record straight after a name is captured from a form.
03

Verify the deliverability of an email address

emailVerifier

What you see in n8n

Notes & use cases

One address in, a deliverability check out. Put this operation between your list and your mailbox rather than after a campaign, and the workflow can route each address on its own merit.

Key parameters

  • Email: the address to verify, in the name@email.com shape shown in the field, or {{ $json.field }} when it comes from the node before.
Use cases
check addresses collected through a form before they reach a mailing list, and send the ones that fail the check to a channel where someone can correct the typo.
Need help

Need help automating Hunter with n8n?

A person reads every message.

FAQ

Hunter and n8n, the questions that come up

01Is the Hunter n8n integration free?
On the n8n side, yes. The Hunter node ships with n8n, so there is nothing to install and no extra n8n cost, on n8n Cloud or on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow built on one runs the same way on the other. What you do need is a Hunter account, because the node authenticates with an API key generated from that account, and what Hunter charges on its own side is a separate question this page does not cover. The node, the credential and the 3 operations add nothing to your n8n bill.
02What credentials does the Hunter node need?
One API key, and that is the only supported authentication method. Create a Hunter account, generate a key from the API keys page in your profile, then add a Hunter credential in the n8n Credentials menu and paste the key into the API Key field. There is no authentication selector on the node itself, so nothing else has to be chosen. Because credentials in n8n live outside workflows, the same entry serves every Hunter node you ever add, and the dropdown on each node is where you pick it. Rotating the key later means editing one credential, not hunting through workflows.
03What are the limits of the Hunter node in n8n?
The first thing to plan for is volume on Domain Search. With Return All switched on, n8n keeps requesting pages from the API until every result for that domain has come through, which is what you want for a full sweep and not what you want on a test run. Switch it off and Limit fixes the maximum number of items returned. The second thing is scope: anything outside these 3 operations goes through the HTTP Request node, which calls any endpoint of the Hunter API and reuses the same credential through predefined authentication.
04Can an n8n workflow react to Hunter in real time?
Not from Hunter itself, because Hunter has no trigger node in n8n. A workflow that uses it starts somewhere else and calls the Hunter node further down. The three usual starters: a Schedule Trigger that runs at a fixed interval, useful for sweeping a list of domains every morning, an n8n Webhook that a third-party service calls when something happens on its side, or the trigger of another tool in your setup, such as a new row or a new deal. From there the Hunter node behaves like any other action node in the chain.
05n8n or Make for Hunter?
It depends on four things, and price is only one of them. Hosting: n8n runs self-hosted with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps prospect data on infrastructure you own. Cost model: Make bills per operation, which matters when a domain sweep returns a lot of results in one run. Visual logic: both draw the workflow on a canvas, and the choice there comes down to how your team thinks. Neither is wrong for Hunter, they just fail differently under scale.
Same platform

Other docs you might need on this stack.

Browse all integrations