Findymail logo

Find Mobile Number by LinkedIn URL (Findymail)

Findymail → Find Mobile Number by LinkedIn URL (Findymail)

POST/v1/findymail-find-phone-from-linkedin-url
texau__findymail-find-phone-from-linkedin-urlenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/findymail-find-phone-from-linkedin-url
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample"
  }
}

Finds phone numbers from a LinkedIn profile URL via Findymail.

Install

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

When to use this.

The "Find Mobile Number by LinkedIn URL" action from Findymail allows users to extract mobile phone numbers directly from a specified LinkedIn profile URL. By providing the input parameter, "linkedin_url," which is the text link to a LinkedIn profile, this action efficiently retrieves the associated phone number. The output, "raw_phone," is presented in a phone format, ensuring easy integration into contact databases or CRM systems. This action is particularly useful for sales professionals, recruiters, and marketers seeking to enrich their lead databases with accurate contact information. Categorized under enrichment, it enhances user outreach efforts by providing essential phone data derived from LinkedIn profiles.

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

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

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/findymail-find-phone-from-linkedin-url
curl -X POST 'https://v3-api.texau.com/api/v1/findymail-find-phone-from-linkedin-url' \
  -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 by LinkedIn URL (Findymail)→Find Email Using LinkedIn URL (Findymail)→Find Email Using Name and Company Domain (Findymail)

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 (findymail) → 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 URL (Findymail)Findymail 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 limit300 / min
  • Per-day limit7,200 / 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.

Heavy tier

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

Related

More Findymail 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__findymail-...` 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 (Findymail) in 60 seconds.

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

Start free →Read the API docs