Leadmagic logo

Find Email by Name and Domain (LeadMagic)

LeadMagic → Find Email by Name and Domain (LeadMagic)

POST/v1/leadmagic-find-email
texau__leadmagic-find-emailenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/leadmagic-find-email
{
  "domain": "https://acme.com",
  "first_name": "Jane",
  "last_name": "Doe"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "status": "valid",
    "message": "sample",
    "has_mx": true,
    "mx_provider": "sample"
  }
}

Finds and validates a professional email address using a name and company domain via LeadMagic.

Install

Add find email by name and domain (leadmagic) 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__leadmagic-find-email

When to use this.

The "leadmagic-find-email" action is designed to efficiently locate and validate professional email addresses using a person's name and their associated company domain. By providing the company domain, first name, and last name as input parameters, users can leverage LeadMagic's powerful email finder endpoint to retrieve accurate email addresses. The output includes essential data fields such as the validated email address, status of the request, a message detailing the process, credits consumed, and information on the MX record and provider. This action is particularly useful for sales and marketing professionals seeking to enrich their contact databases, enhance lead generation efforts, and improve outreach strategies by ensuring they have the correct email addresses for potential clients or partners. As part of the enrichment category, this API action streamlines the process of obtaining reliable contact information, making it an invaluable tool for businesses looking to optimize their communication efforts.

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 (LeadMagic)

Try it

Company domain used to find and verify a professional email address.

First name of the person whose email you want to find.

Last name of the person whose email you want to find.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • email
    Email
    string
  • status
    Status
    text
  • message
    Message
    nullabletext
  • has_mx
    Has Mx
    boolean
  • mx_provider
    Mx Provider
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/leadmagic-find-email. Auth: x-api-key.

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Email by Name and Domain (LeadMagic)→Find Mobile Number using Linkedin Url (LeadMagic)→Validate Email (LeadMagic)

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 (leadmagic) → 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 (LeadMagic)LeadMagic 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 limit3000 / min
  • Per-day limit10,000 / 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 LeadMagic 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__leadmagic-...` 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 (LeadMagic) in 60 seconds.

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

Start free →Read the API docs