OCNORA
Start free

Hunter

CRM & salesAPI keycredential probe

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. Anything not covered by a typed node reaches https://api.hunter.io/v2 through the HTTP node with the same credential.

Connect Hunter freeHunter API docs ↗

Operations 18

  • Create Lead
    Save 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 List
    Create a lead list to file leads under with POST /leads-lists.
    hunter.create_leads_list
  • Delete Lead
    Remove a saved lead with DELETE /leads/{id}. The API acknowledges with 204 and no body.
    hunter.delete_lead
  • Delete Leads List
    Remove a lead list with DELETE /leads-lists/{id}. The API acknowledges with 204 and no body.
    hunter.delete_leads_list
  • Domain Search
    Return 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 Count
    Count 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 Finder
    Find 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 Verifier
    Check 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 Company
    Look 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 Company
    Look 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 Person
    Look 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 Account
    Read 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 Lead
    Read one saved lead by its Hunter id with GET /leads/{id}.
    hunter.get_lead
  • Get Leads List
    Read one lead list by its Hunter id with GET /leads-lists/{id}.
    hunter.get_leads_list
  • List Leads
    Return 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 Lists
    Return the lead lists on the team with GET /leads-lists.
    hunter.list_leads_lists
  • Update Lead
    Change 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 List
    Rename an existing lead list with PUT /leads-lists/{id}.
    hunter.update_leads_list

More in CRM & sales

Run your first Hunter workflow today.

Create a free workspace, add the connection, pick a template or describe the workflow to Build with AI. Workflow Health checks it before it runs.

Start freeBook a demo