Hunter finds the person to write to at a company that visits your site, for Company follow-up, when the contact finders asked before it have nobody there — or on its own, when none of them is connected. Personyze asks Hunter with your own Hunter API key for the people at the company’s web address whose job titles are the ones you chose on Company follow-up’s Who to write to step.
When Hunter is asked
| You connected | Hunter is asked |
|---|---|
| Hunter, and Apollo, ZoomInfo, Lusha or Snov.io | When those have nobody at the company, or cannot answer. |
| Hunter, without any of them | For every company Company follow-up looks up. |
Personyze sends Hunter the company’s web address — nothing about your visitor.
Set it up
- In Hunter, open your account menu, then API keys, and copy a key for Personyze.
- In Personyze, go to Integrations → Marketplace, find Hunter and click Set up.
- Paste the key into Your Hunter API key and click Connect.
Personyze checks the key with Hunter before saving it (Checking…), with a call that uses no search. Once Hunter accepts it, the drawer reads Connected. On an account without the Company follow-up add-on, the drawer says so; a key saved there reads “Saved – used once Company follow-up is on.”
A key that is not a key’s shape is refused at once: “That does not look like a Hunter API key: 16 to 64 letters, digits, dashes and underscores.” One Hunter refuses: “Hunter did not accept this key. Check it is active in Hunter (your account → API keys) and enter it again.”
Your key
The key is stored encrypted and never shown again; only the follow-up opens it. To remove it, click the bin icon beside Connected and confirm.
Verified addresses only
- Hunter is asked for people’s own addresses only, never a shared one such as info@ — up to ten people a company.
- Personyze keeps those whose position names one of your titles, in your titles’ order, a verified address first.
- Only an address Hunter calls valid is emailed. An address Hunter could not check, or one at a server that accepts any address, goes to your rep in an alert instead.
- When the people at a company asked Hunter not to process their data, Hunter gives nobody there, and nobody there is written to.
Searches
- Each company looked up uses one of your Hunter searches.
- Hunter’s answer about a company is kept for 30 days, so the company’s next visits cost nothing.
- Too many requests, or no answer: the company waits an hour and is tried again (contact provider busy). A request Hunter will never take counts as nobody found there.
When Hunter refuses the key, or runs out of searches
With another contact finder connected, Hunter’s trouble never holds up the follow-up: a refused Hunter key is switched off, and the others go on being asked. With Hunter as your only contact finder:
| Hunter | What happens |
|---|---|
| Refuses the key | The key is switched off at once, and the drawer reads “Switched off: Hunter did not accept this key – enter it again, or a new one.” The company reads Hunter key refused on Identified companies, with Check your Hunter key beside it. |
| Has no searches left | The key is switched off rather than retried, and the company reads Hunter out of searches. The drawer reads “Switched off: Hunter’s searches are used up for this period – connect the key again once they renew.” |
While the key is off, the other companies wait, and one that failed on it goes back in the queue on its next visit. Paste a key again and click Connect.
Related
- Company follow-up — the feature Hunter serves
- Apollo — asked first
- ZoomInfo, Lusha and Snov.io — asked after Apollo, before Hunter
- Integrations — every other connection
- App Marketplace — where Hunter’s card is