> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/hunter.md).

# Hunter

Find, verify, enrich, and manage professional email contacts.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Hunter    | API Key        |

#### Hunter

Connect to Hunter to find, verify, enrich, and manage professional contacts.

**Set up in Hunter**

1. Prepare the Hunter account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Key:** Create an API key in the Hunter API dashboard, then paste it here.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Hunter**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                           |
| ------------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| API Key       | Yes      | Create an API key in the Hunter API dashboard, then paste it here. [Provider instructions](https://hunter.io/api-keys). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Hunter** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Find Email Address

Find the most likely work email for a person at a company domain.

**Inputs**

| Field               | Type    | Required | Description                                                                         |
| ------------------- | ------- | -------- | ----------------------------------------------------------------------------------- |
| Company Domain      | string  | Yes      | Company website domain.                                                             |
| First Name          | string  | Yes      | Person's first name.                                                                |
| Last Name           | string  | Yes      | Person's last name.                                                                 |
| Maximum Search Time | integer | No       | Seconds Hunter may spend refining the result. Minimum: 3. Maximum: 20. Default: 10. |

**Outputs**

| Field         | Type    | Description                                                     |
| ------------- | ------- | --------------------------------------------------------------- |
| Found         | boolean | Whether Hunter found an email address.                          |
| Email         | string  | Most likely professional email address.                         |
| Match Details | object  | Hunter's confidence, identity, role, sources, and verification. |

#### Verify Email Address

Check whether an email address is deliverable.

**Inputs**

| Field | Type   | Required | Description              |
| ----- | ------ | -------- | ------------------------ |
| Email | string | Yes      | Email address to verify. |

**Outputs**

| Field                | Type    | Description                                        |
| -------------------- | ------- | -------------------------------------------------- |
| Status               | string  | Hunter's verification status.                      |
| Pending              | boolean | Whether Hunter is still checking the address.      |
| Verification details | object  | Detailed deliverability checks returned by Hunter. |

#### Search Domain Emails

Find professional email addresses associated with a company domain.

**Inputs**

| Field                | Type                      | Required | Description                                                                                                                                                                                       |
| -------------------- | ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Company domain       | string                    | Yes      | Company website domain to search.                                                                                                                                                                 |
| Email type           | select (string)           | No       | Optionally return personal or role-based addresses only. Available values: Personal, Generic.                                                                                                     |
| Seniorities          | multiple\_select (string) | No       | Only return people at the selected seniority levels. Available values: Junior, Senior, Executive.                                                                                                 |
| Departments          | multiple\_select (string) | No       | Only return people in the selected departments. Available values: Executive, IT, Finance, Management, Sales, Legal, Support, HR, Marketing, Communication, Education, Design, Health, Operations. |
| Decision makers only | boolean                   | No       | Filter to decision makers when true, or non-decision-makers when false.                                                                                                                           |
| Maximum results      | integer                   | No       | Maximum contacts to return. Minimum: 1. Maximum: 100. Default: 10.                                                                                                                                |
| Starting offset      | integer                   | No       | Offset returned by a previous search. Minimum: 0. Default: 0.                                                                                                                                     |

**Outputs**

| Field         | Type          | Description                                       |
| ------------- | ------------- | ------------------------------------------------- |
| Emails        | object\_array | Professional email contacts found for the domain. |
| Domain        | string        | Domain resolved by Hunter, if found.              |
| Organization  | string        | Organization associated with the domain.          |
| Email pattern | string        | Common email pattern for the domain.              |
| Total         | integer       | Total matching contacts reported by Hunter.       |
| Next offset   | integer       | Pass this back as Starting offset to continue.    |

#### Enrich Person

Enrich a person profile from an email address.

**Inputs**

| Field | Type   | Required | Description              |
| ----- | ------ | -------- | ------------------------ |
| Email | string | Yes      | Email address to enrich. |

**Outputs**

| Field     | Type   | Description                                                     |
| --------- | ------ | --------------------------------------------------------------- |
| Person    | object | Enriched person, employment, location, and social-profile data. |
| Person ID | string | Hunter identifier for the enriched person.                      |
| Email     | string | Email associated with the person.                               |

#### Create Lead

Create a lead in Hunter for later outreach workflows.

**Inputs**

| Field      | Type     | Required | Description                   |
| ---------- | -------- | -------- | ----------------------------- |
| Email      | string   | Yes      | Lead's email address.         |
| First name | string   | No       | Lead's first name.            |
| Last name  | string   | No       | Lead's last name.             |
| Job title  | string   | No       | Lead's job title.             |
| Company    | string   | No       | Company the lead works for.   |
| Notes      | textarea | No       | Private notes about the lead. |

**Outputs**

| Field      | Type    | Description                             |
| ---------- | ------- | --------------------------------------- |
| Lead ID    | integer | Hunter identifier for the created lead. |
| Email      | string  | Created lead's email.                   |
| First name | string  | First name stored on the lead.          |
| Last name  | string  | Last name stored on the lead.           |
| Job title  | string  | Job title stored on the lead.           |
| Company    | string  | Company stored on the lead.             |
| Notes      | string  | Private notes stored on the lead.       |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/hunter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
