Betterenrich logo

Find Mobile Number by LinkedIn URL

Better Enrich → Find Mobile Number by LinkedIn URL

POST/v1/betterenrich-find-mobile-phone-from-linkedin
texau__betterenrich-find-mobile-phone-from-linkedinenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/betterenrich-find-mobile-phone-from-linkedin
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample",
    "status": "valid",
    "local_format": "sample",
    "country": 1,
    "timezone": "sample"
  }
}

Finds mobile phone numbers from a LinkedIn profile URL using multi-source verification.

Install

Add find mobile number by linkedin url 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-mobile-phone-from-linkedin

When to use this.

The "Find Mobile Number Using LinkedIn URL" action enables users to extract mobile phone numbers from a specified LinkedIn profile URL through a robust multi-source verification process. By inputting the LinkedIn profile URL (linkedin_url), users can efficiently retrieve essential contact information. The action outputs include the mobile number (mobileNumber), status of the retrieval process (status), the local phone format (localFormat), the associated country (country), and the relevant timezone (timezone). This action is particularly useful for sales professionals, recruiters, and marketers seeking to enhance their outreach efforts by obtaining verified mobile contact details from LinkedIn profiles, thereby falling under the enrichment category.

Try it

Run a sample request.

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

Find Mobile Number by LinkedIn URL

Try it

LinkedIn profile URL

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
    text
  • status
    Status
    text
  • local_format
    Local Format
    nullabletext
  • country
    Country
    text
  • timezone
    Timezone
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/betterenrich-find-mobile-phone-from-linkedin. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/betterenrich-find-mobile-phone-from-linkedin
curl -X POST 'https://v3-api.texau.com/api/v1/betterenrich-find-mobile-phone-from-linkedin' \
  -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",
    "status": "valid",
    "local_format": "sample",
    "country": 1,
    "timezone": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Mobile Number by LinkedIn URL→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 mobile number by linkedin url → 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 LinkedIn URLBetter 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 Mobile Number by LinkedIn URL in 60 seconds.

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

Start free →Read the API docs