Fullenrich logo

Find Mobile Number Using LinkedIn Profile URL (FullEnrich)

Full Enrich → Find Mobile Number Using LinkedIn Profile URL (FullEnrich)

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

Discovers mobile phone numbers from a LinkedIn profile URL via FullEnrich.

Install

Add find mobile number using linkedin profile url (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-enrichment

When to use this.

The fullenrich-mobile-number-enrichment action enables users to discover mobile phone numbers associated with a specific LinkedIn profile URL. By providing the linkedin_url parameter, which is the LinkedIn profile URL of the individual you wish to enrich, this action retrieves the corresponding mobile number as output. The output field, mobile_number, is formatted as text, making it easy to integrate into various applications. This action falls under the enrichment category and is particularly useful for sales professionals, recruiters, and marketers looking to enhance their contact databases or establish direct communication with potential leads. By leveraging this API action, users can efficiently gather essential contact information, streamlining outreach efforts and improving engagement strategies.

Try it

Run a sample request.

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

Find Mobile Number Using LinkedIn Profile URL (FullEnrich)

Try it

LinkedIn profile URL of the person to enrich.

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-enrichment. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/fullenrich-mobile-number-enrichment
curl -X POST 'https://v3-api.texau.com/api/v1/fullenrich-mobile-number-enrichment' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"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 Using LinkedIn Profile URL (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 using linkedin profile url (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 Using LinkedIn Profile URL (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 Using LinkedIn Profile URL (FullEnrich) in 60 seconds.

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

Start free →Read the API docs