ModuleX
Integrations
Hunter logo

Hunter integration

Sales · 13 actions · API key auth

Find and verify professional email addresses using the Hunter.io API

Put Hunter to workView Hunter integration docs
Overview

The ModuleX Hunter integration lets a ModuleX agent operate Hunter on your behalf — running create, update and remove actions across account informations, combined enrichments and leads — directly from a plain-English request, using your organization's own Hunter credentials. No pre-built workflow is required: the agent picks the right Hunter action for the task.

Hunter is a sales platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Hunter action — or, when you want a repeatable process, the composer assembles a Hunter workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Hunter in plain English

Type what you want. A ModuleX agent picks the right Hunter action — or chains several — and runs it. No workflow to build.

  • Create a new lead in your Hunter account
    resolves tocreate_lead
  • Find the lead I describe and remove it
    resolves toget_leaddelete_lead
  • Update an existing lead in your Hunter account
    resolves toupdate_lead
  • Show me the leads lists that match what I describe
    resolves toget_leads_list
Use cases

What you can automate with Hunter

  • Find the right lead and remove it in one promptget_leaddelete_lead
  • Look up a leads list on demandget_leads_list
  • Get information about your Hunter accountaccount_information
  • Returns all the information associated with an email address and its domain namecombined_enrichment
  • Create a new lead in your Hunter accountcreate_lead
  • Search all the email addresses corresponding to one website or companydomain_search
At a glance

Hunter integration at a glance

VendorHunter
CategorySales
Actions available13
AuthenticationAPI key
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJun 2026
Reference

All 13 Hunter actions

Account Informations1
account_information
Get information about your Hunter account
Combined Enrichments1
combined_enrichment
Returns all the information associated with an email address and its domain name
Leads5
create_lead
Create a new lead in your Hunter account
delete_lead
Delete an existing lead from your Hunter account
get_lead
Retrieve one of your leads by ID
list_leads
List all your leads with comprehensive filtering options
update_lead
Update an existing lead in your Hunter account
Domain Searches1
domain_search
Search all the email addresses corresponding to one website or company
Email Counts1
email_count
Get the number of email addresses Hunter has for one domain or company
Email Finders1
email_finder
Find the most likely email address from a domain name, a first name and a last name
Email Verifiers1
email_verifier
Check the deliverability of a given email address, verify if it has been found in Hunter's database, and return their sources
Leads Lists2
get_leads_list
Retrieves all the fields of a leads list, including its leads
list_leads_lists
List all your leads lists, sorted with the most recent first

See full parameters and response schemas in the Hunter integration docs

Two ways

Two ways to use Hunter in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Hunter action and runs it — no workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires Hunter into a repeatable workflow you can run on a schedule, from chat, or as an API.
Security

Connecting Hunter

API keyHunter uses API-key authentication. You provide your own Hunter secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Hunter without re-authenticating.

Step-by-step setup in the Hunter docs

Related

Pairs well with Hunter

Agents often chain Hunter with these — connect them once and the agent can use all of them in a single task.

Apollo.io28 actionsFindymail11 actionsGong5 actionsSixtyfour AI4 actionsWiza4 actionsLemlist3 actions
FAQ

Hunter + ModuleX FAQ

A ModuleX agent can run any of Hunter's 13 actions — across account informations, combined enrichments, leads and domain searches — from a plain-English request, using your organization's own Hunter credentials.
No. The agent selects the right Hunter action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.
Via your own Hunter API key, stored encrypted and scoped to your organization.
13, spanning account informations, combined enrichments, leads and domain searches.
Hunter runs on your own credentials, so any Hunter usage is billed by Hunter directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Hunter to work in ModuleX.

Connect Hunter once with your own credentials and let your agent run all 13 actions on demand.

Put Hunter to workView technical docs
Last updated: Jun 2026Browse all 175 integrations →