Fullenrich logo

Find Mobile Number by Name and Domain (FullEnrich)

Full Enrich → Find Mobile Number by Name and Domain (FullEnrich)

POST/v1/fullenrich-mobile-number-using-domain-enrichment
texau__fullenrich-mobile-number-using-domain-enrichmentenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/fullenrich-mobile-number-using-domain-enrichment
{
  "first_name": "Jane",
  "last_name": "Doe",
  "domain": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample"
  }
}

Finds mobile phone numbers using a person's name and company domain via FullEnrich.

Install

Add find mobile number by name and domain (fullenrich) 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__fullenrich-mobile-number-using-domain-enrichment

When to use this.

The "Find Mobile Number Using Person Name and Company Domain (FullEnrich)" action is designed to retrieve mobile phone numbers by leveraging a person's first and last name along with their associated company domain. This enrichment tool requires three key input parameters: the individual's first name, last name, and the company domain (e.g., 'example.com'). Upon execution, the action outputs the corresponding mobile number, providing valuable contact information for business development, recruitment, or networking purposes. This functionality falls under the enrichment category and is particularly useful for sales teams, marketers, and HR professionals seeking to enhance their outreach efforts by obtaining accurate mobile contact details. By integrating this action into your workflow, you can significantly improve your lead generation and relationship-building strategies.

Try it

Run a sample request.

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

Find Mobile Number by Name and Domain (FullEnrich)

Try it

The first name of the person.

The last name of the person.

The company domain name (e.g., 'example.com').

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • mobile_number
    Mobile Number
    string

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/fullenrich-mobile-number-using-domain-enrichment. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/fullenrich-mobile-number-using-domain-enrichment
curl -X POST 'https://v3-api.texau.com/api/v1/fullenrich-mobile-number-using-domain-enrichment' \
  -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": {
    "mobile_number": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Mobile Number by Name and Domain (FullEnrich)→Find Work Email Using LinkedIn Profile URL (FullEnrich)→Find Work Email by Name and Domain (FullEnrich)

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Mobile Number by Name and Domain (FullEnrich)Full 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 limit60 / min
  • Per-day limit1,440 / 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.

Enterprise

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

Related

More Full 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__full 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 Mobile Number by Name and Domain (FullEnrich) in 60 seconds.

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

Start free →Read the API docs