Datagma logo

Find Mobile Number by LinkedIn URL (Datagma)

Datagma → Find Mobile Number by LinkedIn URL (Datagma)

POST/v1/datagma-person-mobile-search
texau__datagma-person-mobile-searchenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/datagma-person-mobile-search
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "http_status_code": "valid",
    "available_source": 1,
    "visible_source": 1,
    "person_count": 1,
    "primary_person_mobile_number": "sample",
    "primary_person_mobile_number_country_code": 1,
    "primary_person_mobile_number_display": "sample",
    "primary_person_mobile_number_display_international": "sample",
    "primary_person_mobile_number_linked_whatsapp": "sample",
    "primary_person_mobile_number_whatsapp": "sample"
  }
}

Finds a mobile phone number using a LinkedIn profile URL or username via Datagma.

Install

Add find mobile number by linkedin url (datagma) 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__datagma-person-mobile-search

When to use this.

The "datagma-person-mobile-search" action enables users to find a person's mobile number by utilizing their LinkedIn profile URL as an identifier. This API action takes a single input parameter, "linkedin_url," which is a string representing the LinkedIn profile of the individual in question. Upon execution, it returns a variety of output fields, including HTTP status code, counts of available and visible sources, and detailed information about the primary phone numbers associated with the person, such as country codes and WhatsApp availability. The data types returned include phone numbers, country codes, and counts, making it suitable for applications in contact enrichment and lead generation. Use cases for this action include enhancing CRM databases, improving networking capabilities, and facilitating outreach efforts by providing verified mobile contact information sourced from LinkedIn profiles. This action falls under the enrichment category, making it a valuable tool for businesses and professionals seeking to expand their contact networks effectively.

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

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
  • http_status_code
    Http Status Code
    nullablenumber
  • available_source
    Available Source
    nullablenumber
  • visible_source
    Visible Source
    nullablenumber
  • person_count
    Person Count
    nullablenumber
  • primary_person_mobile_number
    Primary Person Mobile Number
    array
  • primary_person_mobile_number_country_code
    Primary Person Mobile Number Country Code
    nullablearray
  • primary_person_mobile_number_display
    Primary Person Mobile Number Display
    array
  • primary_person_mobile_number_display_international
    Primary Person Mobile Number Display International
    array
  • primary_person_mobile_number_linked_whatsapp
    Primary Person Mobile Number Linked Whatsapp
    nullablearray
  • primary_person_mobile_number_whatsapp
    Primary Person Mobile Number Whatsapp
    nullablearray

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/datagma-person-mobile-search. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/datagma-person-mobile-search
curl -X POST 'https://v3-api.texau.com/api/v1/datagma-person-mobile-search' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "http_status_code": "valid",
    "available_source": 1,
    "visible_source": 1,
    "person_count": 1,
    "primary_person_mobile_number": "sample",
    "primary_person_mobile_number_country_code": 1,
    "primary_person_mobile_number_display": "sample",
    "primary_person_mobile_number_display_international": "sample",
    "primary_person_mobile_number_linked_whatsapp": "sample",
    "primary_person_mobile_number_whatsapp": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Mobile Number by LinkedIn URL (Datagma)→Find Work Email Using Name and Company Domain (Datagma)→Find Mobile Number Using Email (Datagma)

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 (datagma) → 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 (Datagma)Datagma 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 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 Datagma 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__datagma-...` 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 (Datagma) in 60 seconds.

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

Start free →Read the API docs