Icypeas logo

Find Email by Name and Domain (Icypeas)

IcyPeas → Find Email by Name and Domain (Icypeas)

POST/v1/icypeas-find-email-by-name-and-domain
texau__icypeas-find-email-by-name-and-domainenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/icypeas-find-email-by-name-and-domain
{
  "first_name": "Jane",
  "last_name": "Doe",
  "domain": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "full_name": "sample",
    "status": "valid"
  }
}

Finds an email address using a person's first name, last name, and company domain via Icypeas.

Install

Add find email by name and domain (icypeas) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__icypeas-find-email-by-name-and-domain

When to use this.

The "Find Email by Name and Domain" action from Icypeas enables users to efficiently locate an email address based on a person's first name, last name, and their company domain. This action requires three key input parameters: `first_name`, which specifies the individual's first name; `last_name`, which identifies their last name; and `domain`, representing the company's domain (e.g., icypeas.com). Upon execution, the action returns essential output fields, including the found `email`, `first_name`, `last_name`, `full_name`, and a `status` indicating the success of the operation. This functionality is particularly useful for sales and marketing professionals seeking to enrich their contact databases, streamline outreach efforts, and enhance lead generation strategies. As part of the enrichment category, this action supports businesses in building meaningful connections by providing accurate email addresses linked to specific individuals within organizations.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Find Email by Name and Domain (Icypeas)

Try it

The first name of the target.

The last name of the target.

The company domain (e.g., icypeas.com)

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • email
    Email
    text
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • full_name
    Full Name
    string
  • status
    Status
    string

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/icypeas-find-email-by-name-and-domain. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/icypeas-find-email-by-name-and-domain
curl -X POST 'https://v3-api.texau.com/api/v1/icypeas-find-email-by-name-and-domain' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"first_name":"Jane","last_name":"Doe","domain":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "full_name": "sample",
    "status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Email by Name and Domain (Icypeas)→Enrich→Push to CRM

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → find email by name and domain (icypeas) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Email by Name and Domain (Icypeas)IcyPeas action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit600 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeAsync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Standard tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__icypeas-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Find Email by Name and Domain (Icypeas) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs