Hunter

Operate Hunter through your OOMOL-connected account. This skill calls the hunter connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Hunter. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "hunter" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "hunter" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• account_information — Retrieve information about the authenticated Hunter account.
• combined_enrichment — Retrieve combined person and company enrichment data from Hunter.
• company_enrichment — Retrieve company enrichment data for a domain from Hunter.
• create_lead — Create a new lead in Hunter. [write]
• create_leads_list — Create a new Hunter leads list. [write]
• delete_lead — Delete an existing Hunter lead. [destructive]
• discover_companies — Discover companies in Hunter using a natural-language query or filters.
• domain_search — Search public email addresses for a company domain in Hunter.
• email_count — Count email addresses available for a company domain in Hunter.
• email_finder — Find the most likely professional email address for a person in Hunter.
• email_verifier — Verify the deliverability of an email address in Hunter.
• get_lead — Retrieve a single Hunter lead.
• list_custom_attributes — List custom lead attributes configured in Hunter.
• list_leads — List leads saved in the authenticated Hunter account.
• list_leads_lists — List Hunter leads lists.
• people_enrichment — Retrieve person enrichment data from Hunter by email address or LinkedIn handle.
• update_lead — Update an existing Hunter lead. [write]
• upsert_lead — Create or update a Hunter lead by email address. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Hunter state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: ):

```bash

curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux

```

```powershell

irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell

```

• Not signed in / authentication error — sign in to your OOMOL account once:

```bash

oo auth login

```

• scope_missing / credential_expired / app_not_ready / app_not_found — Hunter is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

```text

https://console.oomol.com/app-connections?provider=hunter

```

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Hunter homepage: https://hunter.io