How to Connect Hunter to n8n

Hunter finds the decision-maker’s email address once a prospect company is qualified. Every enrichment workflow in this library calls it through n8n’s built-in Hunter integration, which needs a single API key.

What you need

• A Hunter account. The free tier includes 25 searches per month as of 2026, enough to verify the connection before you commit to a plan.
• A running n8n instance.
• About 10 minutes.

Get the API key

1. Sign in to Hunter.
2. Click your account avatar in the top right and open the API section.
3. Your key is listed there. Hunter shows it in full at any time, so there is nothing to lose if you navigate away.
4. Copy it.

Hunter keys stay valid until you regenerate them. If a key ever ends up in a screenshot or a shared export, regenerate it from the same page and update n8n.

Create the credential in n8n

1. Go to Credentials and click Add credential.
2. Search for “Hunter” and pick the Hunter API credential.
3. Paste the key.
4. Name the credential “Hunter LGL”. The library’s enrichment workflows reference that exact name.
5. Save.

Test it

n8n ships a native Hunter node, so the cleanest test uses it directly.

1. Add a Hunter node to a blank workflow.
2. Choose the Domain Search operation and enter a domain you know, such as your own company’s.
3. Execute the step.

You should get back the domain’s email pattern and any addresses Hunter has on file, each with a confidence score. An authentication error means the key was mangled in transit; re-copy and update the credential. Note that a successful domain search consumes one search credit, which is why the test uses a single known domain instead of a batch.

Cost and one gotcha

The system pages budget $34 per month for Hunter, which maps to the Starter tier on annual billing at 2026 prices. The gotcha is credit burn from unqualified prospects. Domain searches cost credits regardless of whether the prospect was worth enriching, so the library workflows run Hunter only after the qualification filter has dropped the 40 to 60% of raw records that fail size or fit checks. If you rearrange a workflow, keep Hunter downstream of that filter or your credits will disappear into companies you would never contact.

Where the library uses Hunter

Enrichment workflows across every published system: after sourcing produces a qualified company, Hunter locates the office manager, facility manager, logistics manager, or owner depending on the industry, and passes the address to BetterContact for verification before anything is sent.