Sales & CRM
Find email addresses and manage outreach with Hunter.
Agents find and verify work email addresses, keep lead lists clean, and follow up on outreach. With Hunter triggers, an agent starts when an email from Hunter is sent, opened, clicked, or answered.
5,000 free credits to start.
Agent reach
Hunter API v2
The full surface, searched at run time.
Connect with
- API key
Helios uses the API key to register email and lead webhooks. Hunter requires a Zapier connection to deliver lead creation events.
Event triggers
Yes · 5 events
Plus manual, schedule, and signed webhook.
What the agent can do
What agents do with Hunter
Helios searches the Hunter API v2 at run time. The agent finds the endpoint the task needs and calls it.
- Find and call Hunter API endpoints with your connected API key.
- Find the email addresses Hunter knows for a company domain.
- Find one person's work email from their name and company.
- Verify addresses before they go into a sequence.
- Get a company's logo from its domain.
- Save leads, move them between lists, and update their fields.
- Send an email to a lead and read the replies.
- Start a run when an email is sent, opened, clicked, or answered.
Examples
Tasks you can hand to a Hunter agent
Route every reply
When a lead replies to a sequence, the agent reads the reply, records it in the CRM, and tells the account owner.
When a lead replies to the Q4 outreach sequence, log the reply and alert the owner.
- hunter·read the lead and the email
- attio·find the company record
- attio·add a note with the reply
- slack·message the account owner
Reply from Acme logged
- Note added to the Acme record
- Owner told in Slack that the lead asked for a demo
Find contacts for new accounts
A scheduled agent searches company domains for contacts, verifies their addresses, and saves them as leads.
Every Monday, find and verify contacts at last week's new target accounts and save them as leads.
- attio·list new target accounts
- hunter·search each domain
- hunter·verify the addresses found
- hunter·save leads to the Q4 list
31 leads saved
- 12 accounts searched
- 31 valid addresses saved, 6 invalid ones skipped
Clean a list before a send
The agent verifies addresses in a lead list and moves those Hunter marks as invalid to another list.
Verify every lead in the Webinar list and move invalid ones to a separate list.
- hunter·list leads in the Webinar list
- hunter·verify each address
- hunter·move invalid leads
Webinar list cleaned
- 184 leads checked
- 9 invalid leads moved out
Event triggers
Start a run on Hunter events
Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too.
| Event | What it means |
|---|---|
message.sent | An email from Hunter goes out, from a sequence or from a lead's page. |
message.read | A lead opens an email. Filter on the sequence it came from. |
message.clicked | A lead clicks a link in an email. |
message.replied | A lead replies, so an agent can log it in the CRM and alert the owner. |
lead.created | A lead is created. Hunter sends this only when Hunter Leads is connected to Zapier. |
Works with
Hunter works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on Hunter.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.