Hunter Find Email: Hunter action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Domain domain	string	Required	Domain. Example: stripe.com
First Name first_name	string	Required	First Name. Example: John
Last Name last_name	string	Required	Last Name. Example: Collison

Sample request

{
  "domain": "e.g. stripe.com",
  "first_name": "e.g. John",
  "last_name": "e.g. Collison"
}

Returns

{
  "data": {
    "email": "john@stripe.com",
    "score": 91,
    "domain": "stripe.com",
    "position": "Co-founder",
    "last_name": "Collison",
    "first_name": "John"
  }
}

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

FAQ

Questions about Hunter Find Email.

What does the Hunter Find Email action do in Hunter?

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.

What inputs does Hunter Find Email require?

Required: Domain, First Name, Last Name. 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 Find Email support batch operations?

Yes. Run Hunter Find Email inside a Loop node to process arrays. Tiny Command handles Hunter's rate limits automatically so you don't have to throttle manually.

More actions