Hunter
CRM & salesAPI keyConnection test available
Find, verify and enrich business email addresses with Hunter (API v2).
OCNORA ships 18 typed Hunter operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.hunter.io/v2 through the HTTP node with the same credential.
Before you connect Hunter
- Authentication
- API key
- Credential
- the API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Hunter
Operations, grouped by what they do to your data.
Create and send 2
Read and search 5
Update 2
Delete and cancel 2
Other operations 7
A sample Hunter workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Hunter trigger is needed.
- 2Get Accounthunter.get_accountRead the account behind the connection with GET /account: the plan it is on, when the allowance resets, and how many searches and verifications are left. Use it to stop a workflow before it runs out of credits.
- 3Create Leadhunter.create_leadSave a new lead with POST /leads. The address is the identity: Hunter refuses one that is already on the team, so use this for genuinely new people and Update Lead for the rest.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 18
- Create LeadSave a new lead with POST /leads. The address is the identity: Hunter refuses one that is already on the team, so use this for genuinely new people and Update Lead for the rest.hunter.create_lead
- Create Leads ListCreate a lead list to file leads under with POST /leads-lists.hunter.create_leads_list
- Delete LeadRemove a saved lead with DELETE /leads/{id}. The API acknowledges with 204 and no body.hunter.delete_lead
- Delete Leads ListRemove a lead list with DELETE /leads-lists/{id}. The API acknowledges with 204 and no body.hunter.delete_leads_list
- Domain SearchReturn every email address Hunter knows for a company with GET /domain-search, each with its confidence score and its sources. This is the node that spends one search credit per call.hunter.domain_search
- Email CountCount the addresses Hunter holds for a domain with GET /email-count, broken down by department and seniority. The call is free, so it is the right way to size a domain before spending a search credit.hunter.email_count
- Email FinderFind the most likely email address for one named person at one company with GET /email-finder, and return it with a confidence score and the sources behind it.hunter.email_finder
- Email VerifierCheck whether one address is deliverable with GET /email-verifier, returning the MX, SMTP and disposable-domain checks behind the verdict rather than a bare yes or no.hunter.email_verifier
- Enrich Person and CompanyLook up the person and their company in one call with GET /combined/find, which returns both objects nested under 'person' and 'company'.hunter.enrich_combined
- Enrich CompanyLook up a company by domain with GET /companies/find, returning its industry, size, location, technologies and funding. Hunter answers 404 when it holds no record.hunter.enrich_company
- Enrich PersonLook up the person behind an email address with GET /people/find, returning their name, location, employment and social profiles. Hunter answers 404 when it holds no record, which fails the step so the error edge can handle the miss.hunter.enrich_person
- Get AccountRead the account behind the connection with GET /account: the plan it is on, when the allowance resets, and how many searches and verifications are left. Use it to stop a workflow before it runs out of credits.hunter.get_account
- Get LeadRead one saved lead by its Hunter id with GET /leads/{id}.hunter.get_lead
- Get Leads ListRead one lead list by its Hunter id with GET /leads-lists/{id}.hunter.get_leads_list
- List LeadsReturn one page of saved leads with GET /leads, filtered by list, address or company, or by any other filter key the API documents.hunter.list_leads
- List Leads ListsReturn the lead lists on the team with GET /leads-lists.hunter.list_leads_lists
- Update LeadChange a saved lead with PUT /leads/{id}. Only the fields you fill in are sent; everything else keeps its stored value. The API acknowledges with 204 and no body.hunter.update_lead
- Update Leads ListRename an existing lead list with PUT /leads-lists/{id}.hunter.update_leads_list
Hunter questions
- How does OCNORA authenticate with Hunter?
- With a stored API key credential, shaped the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Hunter?
- 18 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Hunter operation I need is not listed?
- Call https://api.hunter.io/v2 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Hunter?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Hunter calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Hunter workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.