Datagma logo

Find Work Email Using Name and Company Domain (Datagma)

Datagma → Find Work Email Using Name and Company Domain (Datagma)

POST/v1/datagma-find-email
texau__datagma-find-emailenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/datagma-find-email
{
  "domain": "https://acme.com",
  "first_name": "Jane",
  "last_name": "Doe",
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "email_domain": "[email protected]",
    "mxfound": true,
    "smtp_check": true,
    "status": "valid"
  }
}

Finds and verifies a professional email address using a person's name and company domain via Datagma.

Install

Add find work email using name and company domain (datagma) 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__datagma-find-email

When to use this.

The "datagma-find-email" action is designed to locate and verify professional email addresses using an individual's name and their associated company domain through the Datagma platform. This enrichment tool requires key input parameters, including the company domain, first name, and last name of the person, with an optional LinkedIn profile URL for enhanced accuracy. The action outputs essential data fields such as the verified email address, email domain, MX records status, SMTP check results, and a textual status message. Ideal for sales professionals, recruiters, and marketers, this action streamlines the process of connecting with potential leads or candidates by providing reliable email information, making it a vital resource in business communications and outreach strategies.

Try it

Run a sample request.

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

Find Work Email Using Name and Company Domain (Datagma)

Try it

Company name or domain to search the email for.

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

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

LinkedIn profile slug or identifier for the person (optional).

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
  • email_domain
    Email Domain
    string
  • mxfound
    Mxfound
    nullableboolean
  • smtp_check
    Smtp Check
    nullableboolean
  • status
    Status
    string

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/datagma-find-email
curl -X POST 'https://v3-api.texau.com/api/v1/datagma-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","linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "email_domain": "[email protected]",
    "mxfound": true,
    "smtp_check": true,
    "status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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

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 using name and company domain (datagma) → 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 Using Name and Company Domain (Datagma)Datagma 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 limit60 / 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 Datagma 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__datagma-...` 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 Using Name and Company Domain (Datagma) in 60 seconds.

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

Start free →Read the API docs