Hunter is an email marketing company specializing in lead generation and data enrichment.
Hunter is an email marketing company specializing in lead generation and data enrichment. On Nagent, Hunter is exposed as a fully-configurable email integration that any agent can call — 26 actions, and API key authentication. No code is required to wire Hunter into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Hunter to automate the kinds of tasks email teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Hunter into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Hunter, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HUNTER_ACCOUNT_INFORMATIONTool to retrieve information about your Hunter account. Use when you need to check your plan details and usage limits after confirming credentials. Returns `searches.available` and `verifications.available` fields among others; check these before bulk operations to avoid quota exhaustion.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_COMBINED_ENRICHMENTTool to find both person and company information from an email address or LinkedIn handle in a single request. Use when you need complete professional profile enrichment including employment and company details.
Input parameters
The professional's email address to enrich. Either email or linkedin must be provided.
LinkedIn handle as alternative to email. Either email or linkedin must be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_COMPANY_ENRICHMENTTool to get enrichment information for a company by its domain. Use when you need full company details (industry, description, location, metrics) from Hunter.
Input parameters
The domain name for which to retrieve company information. Must be a bare domain (e.g., 'hunter.io') without protocol prefix (https://) or www subdomain.
When provided, the response will be formatted according to Clearbit's schema.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_CREATE_CUSTOM_ATTRIBUTETool to create a new custom lead attribute in your account. Use after deciding on the attribute label.
Input parameters
The name (label) of your custom attribute. Must be unique.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_CREATE_LEADTool to create a new lead. Use after gathering all prospect details to save them to your Hunter account.
Input parameters
The email address of the lead
Internal notes about the lead
Source where the lead was found
Company name of the lead
Twitter handle of the lead (without @)
Domain of the lead's company, e.g. 'reddit.com'
Job title of the lead
Last name of the lead
First name of the lead
Size of the company, e.g. '201-500 employees'
ISO 3166-1 alpha-2 country code
Public LinkedIn profile URL of the lead
Phone number of the lead
ID of a single leads list. Defaults to the last list created if unset
IDs of multiple leads lists. Defaults to the last list created if unset
Industry of the company, e.g. 'Technology', 'Finance'
Probability (0–100) that the email is correct
Map of custom attribute slug to value
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_CREATE_LEADS_LISTTool to create a new leads list. Use when you need to organize leads into a custom list before adding leads.
Input parameters
The name of the leads list to create.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_DELETE_CUSTOM_ATTRIBUTETool to delete an existing custom attribute. Use after confirming the attribute ID to be removed.
Input parameters
Identifier of the custom attribute to be deleted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_DELETE_LEADTool to delete a lead. Use after confirming the lead's ID to remove it from your Hunter.io account.
Input parameters
The unique identifier of the lead to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_DELETE_LEADS_LISTTool to delete a leads list by its ID. Use after confirming the leads list ID to remove it from your Hunter.io account.
Input parameters
Identifier of the leads list to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_DISCOVER_COMPANIESTool to search and retrieve companies matching specified criteria using filters or natural language queries. Use when you need to discover companies from Hunter's B2B dataset based on industry, location, size, or other characteristics.
Input parameters
Maximum number of results to return. Default is 100. Only changeable with Premium.
Natural language search query to find companies. Either query or at least one filter parameter must be provided.
Number of results to skip for pagination. Default is 0. Premium feature only.
Company sizes. Valid values: '1-10', '11-50', '51-200', '201-500', '501-1000', '1001-5000', '5001-10000', '10001+'.
Funding stages: pre_seed, seed, series_a, series_b+, etc. Premium feature only.
Keyword matching mode. Defaults to 'all'.
Funding end date in YYYY-MM-DD format. Premium feature only.
Company name to find similar firms. Premium feature only.
Range end year for company founding. Premium feature only.
Industries to exclude. Use specific industry names like 'IT Services and IT Consulting', 'Financial Services', 'Hospitals and Health Care', 'Construction', 'Restaurants', 'Real Estate', etc. See Hunter's industries.json for the complete list of valid values.
Industries to include. Use specific industry names like 'IT Services and IT Consulting', 'Financial Services', 'Hospitals and Health Care', 'Construction', 'Restaurants', 'Real Estate', etc. See Hunter's industries.json for the complete list of valid values.
Keywords to exclude from search.
Keywords to include in search.
Technology matching mode. Defaults to 'all'.
Maximum funding amount. Premium feature only.
Funding start date in YYYY-MM-DD format. Premium feature only.
List of company names to filter by.
Domain of company to find similar firms. Premium feature only.
Range start year for company founding. Premium feature only.
Technologies to exclude. Premium feature only.
Technologies to include. Premium feature only.
Minimum funding amount. Premium feature only.
List of company domains to filter by.
Company types to exclude.
Company types to include (educational, government agency, non profit, etc.).
Specific years founded. Premium feature only.
Locations to exclude.
Locations to include (continent, business_region, country, state, city).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_DOMAIN_SEARCHTool to search all email addresses for a given domain or company. Use when you need public emails and metadata for outreach or enrichment. Rate-limited; HTTP 429 returned on excess requests — honor the Retry-After header.
Input parameters
Filter by email type. Either 'personal' or 'generic'.
Maximum number of email addresses to return. Default is 10, which is the maximum for free/basic plans. Values above 10 require a paid plan and will fail on free/basic tiers.
Domain name to search for. Required if company not provided.
Number of email addresses to skip. Defaults to 0. Paginate by incrementing offset in steps of limit; end of results when returned count is less than limit.
Company name to search for. Required if domain not provided.
Filter by one or more seniority levels: 'junior','senior','executive'.
Filter by one or more departments, e.g., 'executive','it','finance', etc.
Filter by one or more required fields: 'full_name','position','phone_number'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_EMAIL_COUNTTool to get the total number of email addresses Hunter has for a domain or company with breakdowns by type, department, and seniority. Use when you need email volume statistics without consuming API credits (this call is free).
Input parameters
Filter results to 'personal' or 'generic' emails only.
Domain name to query for email count. Required if company not provided.
Company name to query for email count (minimum 3 characters). Required if domain not provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_EMAIL_FINDERTool to find the most likely email address for a person at a domain or company. Use when you have a person's name and a domain or company and need to infer their email. Results include a confidence score and status; treat emails with status 'accept_all' or 'risky' as lower reliability. Each call consumes API credits — avoid re-enriching the same contact.
Input parameters
Target domain to search for the email (e.g., 'reddit.com'). Takes precedence over company if both are provided.
Company name to search for the email (e.g., 'Reddit'). Used if domain is not provided.
Person's full name. Required if first_name and last_name are not both provided.
Person's last name. Required if first_name is set. Either both first_name+last_name or full_name must be provided.
Person's first name. Required if last_name is set. Either both first_name+last_name or full_name must be provided.
Max duration of the request in seconds (range 320). Longer durations yield more accurate results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_EMAIL_VERIFIERTool to verify the deliverability of an email address. Use when you need to ensure an address is valid and reachable. Response may include statuses `accept_all` or `risky`, indicating uncertain deliverability; do not treat these as fully valid without explicit review. For bulk verification, honor `Retry-After` headers on HTTP 429 responses and use exponential backoff.
Input parameters
The email address to verify.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_GET_CUSTOM_ATTRIBUTETool to retrieve details of a specific custom attribute. Use when you need the label and slug for an attribute ID.
Input parameters
Identifier of the custom attribute, must be a positive integer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_GET_LEADTool to retrieve details of a specific lead by ID. Use after confirming the lead's ID to fetch its full record.
Input parameters
The unique identifier of the lead to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_GET_LEADS_LISTTool to retrieve details of a specific leads list by ID. Use when you need to inspect the contents of an existing leads list.
Input parameters
Identifier of the leads list.
A limit on the number of leads to return. Limit can range between 1 and 100.
The number of leads to skip. Use this parameter to fetch paginated results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_LIST_CAMPAIGNSTool to get all email campaigns in your Hunter account. Campaigns are returned in reverse-chronological order by creation date. Use when you need to retrieve and filter campaigns by status (started/archived) with pagination support.
Input parameters
Number of campaigns to return. Range between 1 and 100. Defaults to 20.
Number of campaigns to skip for pagination. Defaults to 0.
Filter to only return campaigns that have been started. If true, returns only started campaigns. If false, returns only campaigns that have not been started.
Filter to only return campaigns that have been archived. If true, returns only archived campaigns. If false, returns only campaigns that have not been archived.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_LIST_CUSTOM_ATTRIBUTESTool to list all custom lead attributes in your account. Use when you need to retrieve your account's custom lead attributes after authenticating.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_LIST_LEADSTool to list all leads saved in your account with optional filters. Use when you need to retrieve leads with specific criteria after confirming your API key.
Input parameters
Filter leads by email address.
Number of leads to return (1-1000). Defaults to 20.
Search leads by first name, last name, or email.
Number of leads to skip for pagination (0-100000). Defaults to 0.
Filter leads by company name.
Filter leads by Twitter handle.
Filter leads by company website.
Filter leads by position.
Filter leads by last name.
Filter leads by creation date (ISO-8601 format).
Filter leads by first name.
Filter leads by country code (ISO 3166-1 alpha-2).
Filter leads by LinkedIn profile URL.
Filter leads by phone number.
Filter leads by a specific leads list ID.
Filter leads by last activity date (ISO-8601 format).
Filter leads by custom attributes.
Filter leads by last contacted date (ISO-8601 format).
Filter leads with a maximum confidence score (0-100).
Filter leads with a minimum confidence score (0-100).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_LIST_LEADS_LISTSTool to list all leads lists in your account. Use when you need to retrieve and paginate through your leads lists.
Input parameters
A limit on the number of leads lists to be returned. Range between 1 and 100. Defaults to 20.
The number of leads lists to skip for pagination. Defaults to 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_PEOPLE_ENRICHMENTTool to find all information associated with an email address or LinkedIn profile including name, location, job title and social handles. Use when you need to enrich contact data with additional personal and professional details.
Input parameters
The email address for which to find associated information. At least one of email or linkedin_handle must be provided.
When provided, formats response to match Clearbit's schema for consistency.
The LinkedIn profile handle for which to find associated information. LinkedIn handle takes priority when both email and linkedin_handle are provided. At least one of email or linkedin_handle must be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_UPDATE_CUSTOM_ATTRIBUTETool to update an existing custom attribute's label. Use when renaming a custom attribute after creation.
Input parameters
Identifier of the custom attribute, must be a positive integer
The new label for the custom attribute. Must be unique.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_UPDATE_LEADTool to update details of an existing lead by ID. Use when you need to modify saved lead attributes after creation.
Input parameters
Identifier of the lead to update, must be a positive integer
Email address of the lead
Personal notes about the lead
Source where the lead was found
Company name of the lead
Twitter handle of the lead
Website or domain of the lead's company, e.g. 'reddit.com'
Job title of the lead
Last name of the lead
First name of the lead
Size category of the lead's company, e.g. '201-500 employees'
ISO 3166-1 alpha-2 country code of the lead
LinkedIn profile URL of the lead
Phone number of the lead
Identifier of a leads list to assign the lead to
Identifiers of multiple leads lists to assign the lead to
Industry sector of the lead's company, e.g. 'Technology', 'Finance'
Confidence score (0–100) that the email address is correct
Map of custom attribute slugs to their values
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_UPDATE_LEADS_LISTTool to update the name of a specific leads list. Use when renaming an existing leads list.
Input parameters
Identifier of the leads list to update, must be a positive integer
The new name for the leads list
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HUNTER_UPSERT_LEADTool to create or update a lead by email in one call. Use when you want to ensure a lead exists with the provided information without checking its existence first.
Input parameters
The email address of the lead
Internal notes about the lead
Source where the lead was found
Company name of the lead
Twitter handle of the lead (without @)
Domain of the lead's company, e.g., 'reddit.com'
Job title of the lead
Last name of the lead
First name of the lead
Size of the company, e.g., '201-500 employees'
ISO 3166-1 alpha-2 country code
Public LinkedIn profile URL of the lead
Phone number of the lead
ID of a single leads list. Defaults to the last list created if unset
IDs of multiple leads lists. Defaults to the last list created if unset
Industry of the company, e.g., 'Technology', 'Finance'
Probability (0–100) that the email is correct
Map of custom attribute slug to value
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 54 agents privately built on Nagent that already use Hunter.
Build on Nagent
Connect Hunter to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Hunter, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Hunter is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Hunter is connected, you configure its 26 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Hunter steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Hunter event fires, the agent kicks off automatically.
Every Hunter action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Hunter ships with 26 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Hunter together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Hunter-based workflows tailored to your business.