LinkedIn Profile → Phone Number Enrichment

Get a phone number from any LinkedIn profile URL. This Actor runs a multi-source enrichment pipeline behind the scenes: when a usable number is found for a profile, you get it in your results. No match? You pay nothing for that profile.

Why this Actor

Most LinkedIn-to-phone tools depend on a single data path—when it misses, you get nothing. This Actor is built for higher coverage on hard profiles by combining enrichment logic with safe parallel batching, so you can process prospect lists at scale without babysitting one-off lookups.

• Pay only on success — billing applies when a phone is found; misses are not charged
• Single + batch mode — one profile or up to 1,000 URLs per run
• Dry run — test your workflow with mock results, no live enrichment and no charges
• B2B-ready — clean tabular output in the dataset; export to CSV, JSON, Excel, or XML

Requirements

• Apify paid plan required for live enrichment (Starter or above).
• Apify Free plan users can still use dry run mode to preview the output format at no cost.
• If you run live enrichment on a Free plan, the Actor exits gracefully with status: paid_plan_required — no upstream API calls are made.

Input

Field	Type	Description
linkedin_urls	array	LinkedIn profile URLs (/in/...), max 1,000 per run
concurrency	int	Parallel processing (default 10, max 25)
dryRun	bool	Test mode — mock hits, no live calls and no charges. Available on Apify Free plan.

Provide at least one valid LinkedIn profile URL in linkedin_urls.

Example input

{
  "linkedin_urls": [
    "https://www.linkedin.com/in/jane-doe",
    "https://www.linkedin.com/in/john-smith"
  ],
  "concurrency": 10
}

Output

Results appear in the Output tab as a table (default dataset), and can be exported to CSV, JSON, Excel, or XML.

Field	Description
linkedin_url	The LinkedIn profile URL you submitted
phone	The enriched phone when found, otherwise null
status	hit = number found; miss = no usable number; paid_plan_required = Apify Free plan without dry run; payment_required = budget limit; api_error = temporary failure
found	true if a phone was detected for this row
charged	Whether this successful hit was billed on your run

Each row may also include fields such as chargeReason, priceUsd, providerStatus, error, and requestId for transparency and support.

Example output (match)

{
  "linkedin_url": "https://www.linkedin.com/in/jane-doe",
  "phone": "+33612345678",
  "status": "hit",
  "found": true,
  "charged": true
}

Example output (no match)

{
  "linkedin_url": "https://www.linkedin.com/in/john-smith",
  "phone": null,
  "status": "miss",
  "found": false,
  "charged": false
}

Example output (Apify Free plan, live run)

{
  "linkedin_url": "https://www.linkedin.com/in/jane-doe",
  "phone": null,
  "status": "paid_plan_required",
  "found": false,
  "charged": false,
  "error": {
    "code": "PAID_PLAN_REQUIRED",
    "message": "Live enrichment requires an Apify paid plan (Starter or above). Enable dryRun to preview output format for free, or upgrade at https://console.apify.com/billing."
  }
}

Pricing

This Actor uses pay-per-event: you are charged only when a phone number is successfully found for a profile.

From $0.22 per phone number found (USD, store pricing may vary by plan tier.)

Use cases

• Sales & lead gen — turn LinkedIn prospect lists into actionable outreach data
• Recruiting — reach passive candidates beyond LinkedIn InMail, where legally appropriate
• CRM enrichment — append phone numbers to LinkedIn-sourced contacts
• Account-based marketing — enrich target-account decision-makers in batch

Integrations

Works with all standard Apify integrations: Make, Zapier, n8n, webhooks, and the Apify API. Trigger from a CRM update, a Google Sheet row, or any HTTP client.

Notes on usage

• B2B usage only. This Actor is intended for legitimate business purposes—sales prospecting, recruiting, CRM hygiene. Comply with GDPR, local telemarketing rules (in France: Bloctel for B2C), and your jurisdiction’s data protection laws.
• No harassment or unlawful tracking. Do not use this for stalking or non-consensual personal investigation.
• Very large runs. If you push concurrency high, respect rate limits; if a run stops early on an enormous list, check logs and lower concurrency before retrying.

Support

Found a bug or have a feature request? Open an issue on this Actor’s Issues tab on Apify — I respond within 48h.