Start free
ActionHunterUpdated June 2026

How do I verify an email with Hunter?

Short answer: You can hunter verify email in Hunter by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Hunter Hunter Verify Email action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Hunter Verify Email in Hunter — start free All 4 Hunter actions
Hunter Verify Email in Hunter — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Email
email
stringRequiredEmail. Example: john@stripe.com
Sample request
{
  "email": "e.g. john@stripe.com"
}
Returns
{
  "data": {
    "email": "john@stripe.com",
    "score": 95,
    "regexp": true,
    "result": "deliverable",
    "status": "valid",
    "webmail": false,
    "gibberish": false,
    "disposable": false,
    "mx_records": true,
    "smtp_check": true,
    "smtp_server": true
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Hunter Verify Email.

Any of these apps can fire this action as part of a workflow.

Gmail → Hunter
1 Gmail triggers
Slack → Hunter
13 Slack triggers
Google Sheets → Hunter
2 Google Sheets triggers
HubSpot → Hunter
18 HubSpot triggers
FAQ

Questions about Hunter Verify Email.

What does the Hunter Verify Email action do in Hunter?
Validates an email — SMTP-handshake without actually sending. Returns valid/invalid/risky/unknown classification. For pre-flight validation before adding to outbound sequences.
What inputs does Hunter Verify Email require?
Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Hunter returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Hunter Verify Email support batch operations?
Yes. Run Hunter Verify Email inside a Loop node to process arrays. TinyCommand handles Hunter's rate limits automatically so you don't have to throttle manually.
More actions

Other Hunter actions.

Action
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.
Action
Hunter Email Count
Returns just the count without consuming credits. Useful for "is this prospect company worth full enrichment?" pre-flight checks.
Action
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.
Hunter Verify Email in Hunter — start free