How to hunter email count in Hunter

Hunter Email Count 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.

Field	Type	Required	Description
Domain domain	string	Required	Domain

Sample request

{
  "domain": "{{trigger.domain}}"
}

Returns

{
  "data": {
    "total": 150,
    "department": {
      "executive": 10,
      "engineering": 30
    },
    "generic_emails": 50,
    "personal_emails": 100
  }
}

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

FAQ

Questions about Hunter Email Count.

What does the Hunter Email Count action do in Hunter?

Returns just the count without consuming credits. Useful for "is this prospect company worth full enrichment?" pre-flight checks.

What inputs does Hunter Email Count require?

Required: Domain. 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 Email Count support batch operations?

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

More actions