# Find Mobile Numbers from LinkedIn Profile URLs in Bulk

**Use case:** 

Paste LinkedIn profile URLs, one per line, and get the verified mobile number on record for each person, with name, company, location and the profile link. Up to 20,000 profiles per run. Profiles without a number, removed or malformed ones come back as free rows that say why. Numbers are US-centric: about 1 in 4 US decision makers has one. Replace the example URLs with your list.

## Input

```json
{
  "profileUrls": [
    "https://www.linkedin.com/in/jane-doe-example",
    "https://www.linkedin.com/in/john-smith-example",
    "https://www.linkedin.com/in/maria-garcia-example"
  ]
}
```

## Output

```json
{
  "fullName": {
    "label": "Name",
    "format": "string"
  },
  "company": {
    "label": "Company",
    "format": "string"
  },
  "location": {
    "label": "Location",
    "format": "text"
  },
  "phones": {
    "label": "Phone numbers",
    "format": "array"
  },
  "linkedinUrl": {
    "label": "Profile",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The LinkedIn Phone Number Finder — Verified Mobile Numbers, US Actor is ready to run with the inputs already set for "Find Mobile Numbers from LinkedIn Profile URLs in Bulk". [Sign up or log in](https://console.apify.com/create-task-from-example/klkZU6vEK4yisaAWX) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Find Mobile Numbers from LinkedIn Profile URLs in Bulk" task

The LinkedIn Phone Number Finder — Verified Mobile Numbers, US Actor will start running based on the input automatically. You can also change all the input fields, like linkedin profile urls, emails or names, to match your specific use case.

### 3. Receive the "Find Mobile Numbers from LinkedIn Profile URLs in Bulk" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as name, company, location, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Find Mobile Numbers from LinkedIn Profile URLs in Bulk" task via API](https://apify.com/b2bsearch/linkedin-to-phone.md).

## FAQ

### What does the LinkedIn URL to mobile number task return?

The LinkedIn URL to mobile number task returns one row per profile: the verified mobile numbers on record, name, company, location and the profile URL. A profile with no number comes back as a free row with the reason.

### How many LinkedIn profiles have a mobile number on record?

Coverage is US-centric: in the LinkedIn URL to mobile number task about 1 in 4 US decision makers has a verified mobile number on record, and matches outside the US are rare. Only profiles returned with a number are charged.

### What input formats does the task accept besides profile URLs?

The LinkedIn URL to mobile number task reads one entry per line: a full profile URL, a bare handle, an email address, or a name with the company domain, such as Jane Smith, acme.com. Up to 20,000 entries per run.

### Do I need a LinkedIn account, cookies or a browser extension?

The LinkedIn URL to mobile number task looks numbers up in a professional profile database, so it needs no LinkedIn login, cookies or extension and never opens the profiles themselves.

### How do I run the task through the API or on a schedule?

Copy the LinkedIn URL to mobile number task to your Apify account, then start it from the Apify API, the MCP server, n8n, Make or Zapier, or on a schedule. Each run writes a dataset you can export as CSV, Excel or JSON.

## About this Actor

This example demonstrates how to use [LinkedIn Phone Number Finder — Verified Mobile Numbers, US](https://apify.com/b2bsearch/linkedin-to-phone.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/b2bsearch/linkedin-to-phone.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/b2bsearch/linkedin-to-phone.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).