Hunter.io

undefined

Detail	Value
Category	Data
Base URL	https://api.hunter.io/v2
Authentication	API Key (Query)
Endpoints	7
Connector key	hunter-io

Using Hunter.io in a workflow

1. Go to Connections and click New Connection.
2. Pick Hunter.io from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET	Domain Search
GET	Email Finder
GET	Email Verifier
GET	Email Count
GET	Leads
GET	Lead Lists
GET	Campaigns

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Domain Search

Detail	Value
Operation ID	domain_search_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select domain_search_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Email Finder

Detail	Value
Operation ID	email_finder_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select email_finder_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Email Verifier

Detail	Value
Operation ID	email_verifier_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select email_verifier_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Email Count

Detail	Value
Operation ID	email_count_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select email_count_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Leads

Detail	Value
Operation ID	leads_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select leads_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Lead Lists

Detail	Value
Operation ID	lead_lists_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select lead_lists_5.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.

GET

Campaigns

Detail	Value
Operation ID	campaigns_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hunter.io connection from the Connection dropdown.
3. In the Operation dropdown, select campaigns_6.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hunter.io API reference.