Findymail logo

Find Email Using Name and Company Domain (Findymail)

Findymail → Find Email Using Name and Company Domain (Findymail)

POST/v1/findymail-find-email-from-name-domain
texau__findymail-find-email-from-name-domainenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/findymail-find-email-from-name-domain
{
  "unique_name": "Jane Doe",
  "domain": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]"
  }
}

Finds a professional email address using a person's full name and company domain via Findymail.

Install

Add find email using name and company domain (findymail) 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__findymail-find-email-from-name-domain

When to use this.

The "Find Email Using Name and Company Domain" action from Findymail enables users to efficiently locate email addresses based on a contact's full name and their associated company domain. This API action requires two key input parameters: 'name', which is the complete name of the individual, and 'domain', representing the company’s web domain. Upon execution, the action returns the corresponding email address, categorized under the semantic type 'email'. This functionality is particularly valuable for sales teams, marketers, and recruiters seeking to enrich their contact databases or enhance outreach efforts. By leveraging this API, users can streamline their communication strategies and improve lead generation processes, making it an essential tool in the enrichment category.

Try it

Run a sample request.

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

Find Email Using Name and Company Domain (Findymail)

Try it

Full name of the contact

Company domain

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

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/findymail-find-email-from-name-domain. Auth: x-api-key.

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Email Using Name and Company Domain (Findymail)→Find Mobile Number by LinkedIn URL (Findymail)→Find Email Using LinkedIn URL (Findymail)

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 using name and company domain (findymail) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Email Using Name and Company Domain (Findymail)Findymail 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 limit300 / min
  • Per-day limit7,200 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

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.

Related

More Findymail actions.

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__findymail-...` 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 Using Name and Company Domain (Findymail) in 60 seconds.

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

Start free →Read the API docs