EmailReal-timeUpdated May 2026

Hunter

Hunter.io email finder and verifier

Hunter is the email-finder service used by SDRs and growth teams to find professional email addresses for outbound prospecting — feed it a person + company, get the most likely email back with a confidence score. Tiny Command exposes four actions, no triggers: Find Email (best-guess email for a given first_name, last_name, domain — returns the email with a confidence score and the matching pattern Hunter inferred, e.g., "{first}.{last}@domain.com"), Verify Email (validates an email address — checks MX records, SMTP-level deliverability without sending, returns a status of valid/invalid/risky/unknown with sub-scores), Domain Search (returns every email Hunter has indexed for a domain — paginated, with each email's source URLs and confidence), Email Count (returns the count of emails Hunter has indexed for a domain without returning the emails — useful for ICP-fit pre-checks). The connection uses a Hunter API key from the user account. Workflows commonly chain Find Email → Verify Email to ensure the inferred email is real before adding to a sequence.

Connect Hunter

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Hunter can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Hunter Domain Search	Returns every email Hunter has indexed for a domain with source attribution and confidence scores. For "build a prospect list for Acme Co" sourcing workflows.	1 fields	View →
Hunter Email Count	Returns just the count without consuming credits. Useful for "is this prospect company worth full enrichment?" pre-flight checks.	1 fields	View →
Hunter Find Email	Best-guess email for a name + domain using Hunter's inferred email pattern. Returns email + confidence score. The standard hook for "I have a name and company → find their email" sales workflows.	3 fields	View →
Hunter Verify Email	Validates an email — SMTP-handshake without actually sending. Returns valid/invalid/risky/unknown classification. For pre-flight validation before adding to outbound sequences.	1 fields	View →

Recipes

Pre-built Hunter workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Hunter → Slack alerts

AI-triage every Hunter event, ping the right channel only when it matters.

Hunter → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Hunter → Notion database

Turn Hunter into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Hunter once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Hunter field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Hunter integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Hunter to Tiny Command?

Open the Tiny Command workflow builder, drop in a Hunter node, and click Connect. Authorize Hunter once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Hunter triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Hunter today. Use Tiny Command's universal Webhook or Schedule trigger to start Hunter workflows, then run any Hunter action you need.

What Hunter actions can I run from a workflow?

4 Hunter actions are available out of the box, covering email operations like "Hunter Domain Search". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Hunter integration real-time?

Hunter actions execute synchronously inside your workflow. Tiny Command waits for Hunter's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Hunter with Tiny Command?

No. Every Hunter trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Hunter API endpoint directly.

How much does the Hunter integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Hunter integration itself has no per-app surcharge.