enrich_find_email

Pack: enrich-waterfall · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/enrich_find_email for the schema, then POST the same URL with its arguments for the data.

Find a person’s work email. Step 0 is FREE and needs no key: a labelled “inferred” guess from the domain’s known email pattern (via Hunter’s domain-pattern lookup, or a default guess). Then tries your own vendor accounts in order (hunter, findymail, peopledatalabs, snov, prospeo, leadmagic, icypeas, trykitt), stopping at the first CONFIRMED hit. Every response carries provider_hit, attempts[] with per-attempt cost, and stopped_because. Pipeworx charges 0 credits. Example: enrich_find_email({ full_name: “Patrick Collison”, domain: “stripe.com”, _hunterKey: “your-hunter-key” })

Parameters

NameTypeRequiredDescription
full_namestringyesThe person’s full name, e.g. “Patrick Collison”.
domainstringyesCompany mail domain, no protocol, e.g. “stripe.com”.
companystringnoCompany NAME, e.g. “Stripe”. Optional; defaults to the domain.
orderarraynoVendor order for the PAID waterfall, tried left to right (step 0 pattern inference always runs first regardless). Defaults to [“hunter”,“findymail”,“peopledatalabs”,“snov”,“prospeo”,“leadmagic”,“icypeas”,“trykitt”].
itemsstringno
stop_on_first_hitbooleannoDefault true: stop at the first vendor that returns an address. Set false to query every vendor you supplied a key for.
_hunterKeystringnoYour hunter.io API key. Also reused (free, no extra charge) for the free step-0 pattern lookup, if supplied — omit it and step 0 still runs, falling back to a default pattern guess.
_findymailKeystringnoYour findymail API key.
_pdlKeystringnoYour People Data Labs API key.
_snovKeystringnoYour snov.io credentials as “client_id:client_secret”.
_prospeoKeystringnoYour Prospeo API key.
_leadmagicKeystringnoYour LeadMagic API key.
_icypeasKeystringnoYour Icypeas API key.
_trykittKeystringnoYour TryKitt API key.

Example call

Arguments

{
  "full_name": "Patrick Collison",
  "domain": "stripe.com",
  "order": [
    "findymail",
    "hunter"
  ],
  "_hunterKey": "your-hunter-api-key",
  "_findymailKey": "your-findymail-api-key"
}

curl

curl -X POST https://gateway.pipeworx.io/enrich-waterfall/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"enrich_find_email","arguments":{"full_name":"Patrick Collison","domain":"stripe.com","order":["findymail","hunter"],"_hunterKey":"your-hunter-api-key","_findymailKey":"your-findymail-api-key"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('enrich_find_email', {
  "full_name": "Patrick Collison",
  "domain": "stripe.com",
  "order": [
    "findymail",
    "hunter"
  ],
  "_hunterKey": "your-hunter-api-key",
  "_findymailKey": "your-findymail-api-key"
});

More examples

{
  "full_name": "Sarah Chen",
  "domain": "google.com",
  "company": "Google",
  "stop_on_first_hit": false,
  "_pdlKey": "your-peopledatalabs-api-key",
  "_hunterKey": "your-hunter-api-key"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the enrich-waterfall pack
{
  "mcpServers": {
    "enrich-waterfall": {
      "url": "https://gateway.pipeworx.io/enrich-waterfall/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 10, 2026