Short answer: You can hunter find email in Hunter by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Hunter Hunter Find Email action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
{"domain": "e.g. stripe.com","first_name": "e.g. John","last_name": "e.g. Collison"}
{"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.
Any of these apps can fire this action as part of a workflow.