Hunter

What your agents can doCopy Anchor Link

Helios agents use your connected API key to find and verify email addresses, manage leads, and call Hunter's API. They can also retrieve company logos.

• Find the email addresses Hunter knows for a company domain
• Find one person's work email from their name and company
• Verify an address before it goes into a sequence
• Save leads, move them between lists, and add them to a sequence
• Send one email to a lead from a connected email account
• Read the emails a sequence sent and the replies leads wrote back
• Get a company's logo from its domain

Searches and verifications use the credits on your Hunter plan. Managing leads, lists, and sequences is free.

The agent's API tool reaches api.hunter.io and the Logo API at logos.hunter.io. A logo comes back as an image file that the agent saves in its working directory.

AuthenticationCopy Anchor Link

See Integration authentication for how credentials are stored and injected.

Hunter API KeyCopy Anchor Link

Hunter API keys are personal. A key belongs to the user who created it, and calls with it use the credits your team shares.

Hunter API keys have no scopes or permissions to choose. A key can call every endpoint as the user who owns it. What Hunter returns depends on that user's role and your plan:

• Role: a team owner or admin can read the whole team's request history. A regular member sees only their own requests.
• Paid plan: the agent sees every email account on the team. On the Free plan it sees only the key owner's accounts, and Domain Search returns at most 10 results.
• Premium plan: Discover's paging and some of its filters need it.
• AI writing assistant: turning on the AI assistant for a sequence needs a plan that includes it.

1. In Hunter, open your account's API keys page.
2. Copy a key, or create one for Helios.
3. In Helios, choose Hunter API Key, paste the key into Hunter API Key, and save.

Helios registers the webhooks for triggers with the same key. If you delete the key in Hunter, create a new one and enter it through Manage.

TriggersCopy Anchor Link

Hunter can start a Workflow when an email from Hunter is sent, opened, clicked, or answered, and when a lead is created. The email events cover emails sent from a sequence and emails sent one at a time from a lead's page. When you save the connection, Helios registers one webhook for each event through Hunter's webhook API, so there is nothing to set up in Hunter. Deleting the connection removes them.

Hunter's webhooks are team-wide. They fire for emails and leads from every member of your Hunter team, not only the key's owner. Hunter doesn't offer webhooks on its Data Plans.

All filters are optional.

• Sequence matches emails from the sequences you choose from the list. An email sent from a lead's page belongs to no sequence, so this filter never matches it.
• Recipient email matches the address the email went to, such as *@acme.com. Case doesn't matter. Hunter leaves the address out when the recipient asked Hunter to stop processing it, or when Hunter can't check that at delivery time. The filter doesn't match those events.
• Lead email matches the new lead's email address, such as *@acme.com. Case doesn't matter. It doesn't match a lead without an address.

Hunter records opens only when the sequence tracks opens, and clicks only when it tracks links. Link tracking needs a paid Hunter plan, Starter or above. Hunter doesn't record an open from the same browser within 10 seconds of the last one, opens and clicks from the sender's IP addresses, or anything after 100 opens or 100 clicks on one email.

Hunter's webhook API is in beta. Hunter doesn't sign deliveries. Each webhook URL that Helios registers contains a random secret, and that secret is the only check that a delivery comes from Hunter. Helios rejects deliveries without it. Hunter can send the same event more than once, and Helios drops the repeats.

Hunter's docs say it sends lead.created only when Hunter Leads is connected to Zapier. See Hunter's Zapier guide. Helios registers the webhook for it either way. While Hunter lists no Zapier connection, the trigger picker shows lead.created as unavailable. After you connect Zapier, open the connection, click Manage, and save. Hunter doesn't document the body of this event.

Hunter deletes a webhook as soon as a delivery gets a 410 response, and when deliveries still fail 10 days after the first failure. It emails the webhook's owner when it does. Helios doesn't register a deleted webhook again by itself. Open the connection, click Manage, and save to register all the webhooks again.

Check that it worksCopy Anchor Link

• The connection: after you save, the connection's status shows Connected. Error means the connection test failed.
• A trigger:
  1. Add message.sent to a workflow with no filters.
  2. Send an email to a lead from Hunter.
  3. Check that a run starts. Then open the connection in Helios and click Webhook events to see the event.
• Hunter's side: Hunter lists webhooks under Webhooks in the Sequences settings, and marks one that can't deliver as Failing.

Common errorsCopy Anchor Link

LimitsCopy Anchor Link

Hunter limits each endpoint separately. Domain Search and Email Finder allow 15 requests a second and 500 a minute, and Email Verifier allows 10 a second and 300 a minute. Sending a single email allows 10 requests in 10 minutes. Searches and verifications also use your plan's monthly credits. See Hunter's API documentation and pricing.