Resources · Make integration

Hunter Make integrationAutomate Hunter with Make.

Can Make find a prospect's email, check it and save it as a lead in Hunter on its own? Yes. The Hunter Make integration gives you 11 modules: 1 trigger, 8 actions and 2 searches. This page walks you through the connection, a first working scenario and every module.

Try the Hunter integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Hunter Make integration?

The Hunter Make integration links your Hunter account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. Once linked, Make can call Hunter for you whenever your other apps hand it a new prospect, so nobody copies addresses by hand.

A clean lead from a bare name. A sales rep drops a prospect in a spreadsheet. Find an Email looks for the address, then Create a Lead stores it in Hunter, ready for outreach.

Fewer bounces before a send. Before a list goes out, Verify an Email checks each address, and Update a Lead writes the outcome back, so doubtful contacts stay out of the campaign.

A campaign that fills itself. Watch Campaigns keeps an eye on your Hunter campaigns, and Add Recipients pushes new contacts into the right one without a trip to the dashboard.

The official documentation gives no description for these modules, so their names are the only guide. When a module falls short, Make an API Call reaches the rest of the Hunter API with the same connection. Hunter also has a node in n8n: compare both on the Hunter n8n integration page and in the n8n vs Make comparison, and check plan limits on Make pricing.

Connect

How do you connect Hunter to Make?

  1. 01

    Copy your Hunter API key

    You need an active Hunter account. Log in, open your account dashboard, go to the API keys section and copy the key shown on screen. Keep that tab open, you will paste the key in a moment.

  2. 02

    Add a Hunter module in Make

    In your scenario, add any Hunter module and click Create a connection. The Connection name field is optional; a name like the account owner helps when a teammate opens the scenario later.

  3. 03

    Paste the key and save

    Paste the API key into the credentials field and confirm. That connection, your Hunter account linked to Make once, is now reused by every Hunter module you add, so you only do this step one time.

First scenario

Build your first scenario with Hunter

GoalWhen a new prospect lands in your list, Make finds their email with Hunter and saves them as a lead.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the app where your prospect list lives, a spreadsheet or your CRM, and choose its module that brings in new rows.

  2. 02

    Add Find an Email

    Click the + on the right of that first module, search for Hunter and pick Find an Email. Create the connection with your API key, then map the prospect details from the previous module.

  3. 03

    Store the result with Create a Lead

    Add Create a Lead after the search. Make lists what it can fill once the connection exists; map the address returned by Find an Email and the prospect details you already have.

  4. 04

    Test with Run once

    Add one test prospect to your list and click Run once. Open each module bubble to read the bundle it received, one item passed along, and check that the lead appears in Hunter.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Triggers

Hunter trigger in Make

1 module starts a scenario when something happens in Hunter. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Hunter as soon as it happens.

Hunter1Watch Campaigns

Watch Campaigns

triggerIn the docs only

Watch Campaigns is the only way to start a scenario from Hunter itself: it follows your Hunter campaigns and passes what it finds to the next module. The documentation lists it without a description, so its scheduled type and what it returns are read from its name: check both before you build on it.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan.
When to use it
you want your team or another tool to follow what happens on your outreach campaigns without opening Hunter.
Watch out
click Run once first and open the bundles to see exactly which campaign details come through.
Modules

Hunter modules in Make

Hunter gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Hunter1

Add Recipients

ActionIn the docs only

Add Recipients puts contacts into one of your Hunter campaigns straight from a scenario, so a prospect qualified elsewhere joins the sequence right away.

When to use it
a deal stage changes in your CRM and that contact should start receiving the campaign.
Watch out
the doc gives no detail on its fields; run it on a single test contact before feeding a whole list.
Hunter2

Count Emails

ActionIn the docs only

Going by its name, Count Emails tells you how many addresses Hunter holds for what you ask about, which lets the scenario decide whether a search is worth running at all.

When to use it
you screen target companies and want to skip those with nothing to find before spending operations on deeper lookups.
Watch out
it returns a count, not the addresses; pair it with a search module when you need the contacts.
Hunter3

Create a Lead

ActionIn the docs only

Create a Lead saves a new prospect in your Hunter leads, so contacts gathered by other apps end up in one place for outreach.

When to use it
right after Find an Email, to keep the address it found along with the person's details.
Watch out
the same prospect arriving twice may create two leads; run Search Leads first when your source can repeat entries.
Hunter4

Delete a Lead

ActionIn the docs only

Delete a Lead removes a prospect from your Hunter leads, which keeps your list free of contacts who asked to be left alone or left the company.

When to use it
someone unsubscribes in another tool and must disappear from Hunter as well.
Watch out
Test with a dummy lead first and point it only at the lead you mean to remove.
Hunter5

Find an Email

SearchIn the docs only

Find an Email turns the prospect details you already have into an address you can write to, which is often the first job people hand to this integration.

When to use it
a new row arrives with a person and a company but no email.
Watch out
as a search, it can come back empty; add a filter after it so Create a Lead only runs when an address was found.
Hunter6

Get a Lead

ActionIn the docs only

Get a Lead fetches one lead you can already identify, handing its current details to the modules that follow.

When to use it
another tool stored the lead's reference and you need its latest data before writing a reply or updating a record.
Watch out
it reads a single known lead; to look through your leads by criteria, choose Search Leads instead.
Hunter7

Make an API Call

ActionIn the docs only

Make an API Call lets you call any endpoint of the Hunter API with the connection you already set up, covering what the ten other modules leave out.

When to use it
you need a Hunter feature that has no dedicated module in this list.
Watch out
here you build the request yourself, so keep the Hunter API documentation open and test with Run once before activating.
Hunter8

Search Leads

SearchIn the docs only

Search Leads looks through your Hunter leads and returns every match, so a scenario can check what already exists before it writes anything.

When to use it
before Create a Lead, to avoid storing a prospect you already have.
Watch out
it can return zero, one or several bundles, and each following module then runs once per bundle, which adds operations.
Hunter9

Update a Lead

ActionIn the docs only

Update a Lead changes an existing Hunter lead, so the record keeps pace with what your other tools learn about the prospect.

When to use it
Verify an Email has just checked an address and you want the lead to reflect the outcome.
Watch out
it needs to know which lead to change; get that reference from Search Leads or Get a Lead earlier in the flow.
Hunter10

Verify an Email

ActionIn the docs only

Verify an Email checks an address before you rely on it, which protects your sender reputation when a list comes from a form or an import.

When to use it
a batch of contacts is about to join a campaign through Add Recipients.
Watch out
read the returned bundle in Run once and add a filter so only the addresses you judge safe move on.
Need help

Need help automating Hunter with Make?

A person reads every message.

FAQ

Hunter and Make: common questions

01Is the Hunter Make integration free?
Yes, on the Make side. Hunter is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in operations each month. Your Hunter subscription is a separate matter: the Hunter pricing page covers it, and this page quotes no price for either tool.
02What do you need to connect Hunter to Make?
An active Hunter account and its API key. Log in to Hunter, open your account dashboard, go to the API keys section and copy the key. In Make, add any Hunter module, click Create a connection, give it a name if you like and paste the key. The same connection then serves every Hunter module in all your scenarios, so if the key ever changes, you only update it in one place.
03Does the Hunter Make integration trigger fire in real time?
No. Watch Campaigns is, judging by its name, a scheduled trigger: Make checks Hunter on the scenario's schedule, shown by the clock badge on the module. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Hunter has no instant trigger in Make, so if you need a faster start, open the flow on the app where the event happens and call Hunter modules after it.
04What if the Hunter module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Hunter API with the connection you already created, so you do not need a second key. The 10 listed modules cover leads, email search, verification, counting and campaign recipients; anything else goes through that module. The documentation also warns that its content is AI-generated from Hunter's own docs and may contain mistakes, so check important details with Hunter directly and test each scenario with Run once.
05Should you use Make or n8n for Hunter?
It depends on the tool your team already runs. Hunter is available in Make with 11 modules, including one scheduled trigger and Make an API Call for the rest of the API. Hunter also has a node in n8n. Compare the modules each side offers against the scenario you have in mind, and see whether the trigger you need exists. If your other automations already live in one of the two, keeping Hunter there means one place to monitor and fix.
Same platform

Other docs you might need on this stack.

Browse all integrations