Leadmagic logo

Find Mobile Number using Linkedin Url (LeadMagic)

LeadMagic → Find Mobile Number using Linkedin Url (LeadMagic)

POST/v1/leadmagic-find-mobile-number
texau__leadmagic-find-mobile-numberenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/leadmagic-find-mobile-number
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample",
    "profile_url": "https://acme.com",
    "message": "sample"
  }
}

Finds a person's mobile number and email using their LinkedIn profile URL or username.

Install

Add find mobile number using linkedin url (leadmagic) 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__leadmagic-find-mobile-number

When to use this.

The "leadmagic-find-mobile-number" action is designed to enhance lead enrichment by retrieving a person's mobile number and email address using their LinkedIn profile URL or username. By inputting the LinkedIn URL (text), users can seamlessly access valuable contact information. The output includes the mobile number (phone), the LinkedIn profile URL (url), and a message (text) confirming the action's success or failure. This action is particularly useful for sales professionals, recruiters, and marketers seeking to connect with potential leads or candidates, making it an essential tool in the enrichment category. With its focus on extracting critical contact details, this API action streamlines outreach efforts and enhances networking capabilities.

Try it

Run a sample request.

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

Find Mobile Number using Linkedin Url (LeadMagic)

Try it

The LinkedIn profile URL or username of the person.

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
  • profile_url
    Profile Url
    text
  • message
    Message
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/leadmagic-find-mobile-number. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/leadmagic-find-mobile-number
curl -X POST 'https://v3-api.texau.com/api/v1/leadmagic-find-mobile-number' \
  -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",
    "profile_url": "https://acme.com",
    "message": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Mobile Number using Linkedin Url (LeadMagic)→Find Email by Name and Domain (LeadMagic)→Validate Email (LeadMagic)

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 url (leadmagic) → 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 Url (LeadMagic)LeadMagic 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 limit3000 / 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.

Heavy tier

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

Related

More LeadMagic 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__leadmagic-...` 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 Url (LeadMagic) in 60 seconds.

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

Start free →Read the API docs