Betterenrich logo

Find Work Email by Name and Domain

Better Enrich → Find Work Email by Name and Domain

POST/v1/betterenrich-find-work-email-from-fullname-company-domain
texau__betterenrich-find-work-email-from-fullname-company-domainenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/betterenrich-find-work-email-from-fullname-company-domain
{
  "full_name": "Jane Doe",
  "domain": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "status": "valid",
    "verifier": "sample",
    "esp": "sample"
  }
}

Finds business email addresses using a person's full name and company domain.

Install

Add find work email by name and domain 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__betterenrich-find-work-email-from-fullname-company-domain

When to use this.

The "Find Work Email Using Full Name and Company Domain" action is designed to efficiently retrieve business email addresses by leveraging a person's full name and their associated company domain. This enrichment tool requires two key input parameters: 'full_name', which is the complete name of the individual, and 'domain', representing the company's domain. Upon execution, the action outputs the corresponding 'email' address, along with 'status', 'verifier', and 'esp' (Email Service Provider) information. This functionality is particularly useful for sales teams, recruiters, and marketing professionals seeking to enhance their outreach efforts by accurately identifying and validating professional email contacts. By streamlining the process of finding work emails, this action falls under the enrichment category, facilitating improved communication strategies and lead generation initiatives.

Try it

Run a sample request.

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

Find Work Email by Name and Domain

Try it

Full name of the person

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
  • status
    Status
    text
  • verifier
    Verifier
    nullabletext
  • esp
    Esp
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/betterenrich-find-work-email-from-fullname-company-domain. Auth: x-api-key.

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Work Email by Name and Domain→Verify Catch-All Email→Find LinkedIn URL by Name

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 work email by name and domain → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Work Email by Name and DomainBetter Enrich 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 limit500 / min
  • Per-day limit12,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.

Heavy tier

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

Related

More Better Enrich 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__better enrich-...` 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 Work Email by Name and Domain in 60 seconds.

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

Start free →Read the API docs