# LinkedIn People & Company Lead Suite (`muhammadafzal/linkedin-people-company-lead-suite`) Actor

Extract public LinkedIn person and company lead records from supplied URLs using direct public-page parsing first, with an optional ScrapeCreators fallback when LinkedIn blocks or omits usable data.

- **URL**: https://apify.com/muhammadafzal/linkedin-people-company-lead-suite.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Lead generation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 linkedin lead records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn People & Company Lead Suite

Extract structured public LinkedIn person and company lead records from supplied URLs for CRM enrichment, recruiting research, account research, and lead qualification.

### What it returns

Each dataset item contains `recordType`, `source`, `linkedinUrl`, `name`, `headline`, `location`, `about`, `followers`, `companyId`, `employeeCount`, `industry`, `website`, `description`, `logoUrl`, and `rawFields`.

### Input

Provide one or more public URLs in `personUrls` and/or `companyUrls`. The Actor accepts up to 50 total records. `fallbackMode` defaults to `fallback`: it tries a direct public HTML extraction first and then uses ScrapeCreators only when the direct path is blocked or has no usable identity fields. Set `providerOnly` to use the provider for every URL, or `direct` to disable the provider.

The fallback reads `SCRAPECREATORS_API_KEY` from the Actor environment. Do not put API keys in input, URLs, README files, or source code.

### Example input

```json
{
  "personUrls": ["https://www.linkedin.com/in/example/"],
  "companyUrls": ["https://www.linkedin.com/company/shopify/"],
  "fallbackMode": "fallback",
  "maxResults": 25
}
```

### Public-data limits and compliance

This Actor uses only public pages or an authorized public-data provider. It does not log in, accept LinkedIn cookies, bypass CAPTCHAs or challenges, or claim access to private member data. LinkedIn public pages may omit current job titles and work history; unavailable values are returned as `null`. Use the data lawfully, respect applicable LinkedIn/provider terms, and honor privacy, opt-out, and retention requirements.

### Pricing

The primary PPE event is one validated lead record delivered to the default dataset at $0.01. A run start event may also apply according to the Actor’s live Apify monetization configuration. Provider credit usage, when the fallback is used, is separate from this Actor event price and should be measured before publication.

### Failure behavior

Blocked or unavailable pages produce warnings in the `SUMMARY` key-value record and do not create fabricated dataset rows. Invalid URL sets are rejected before result charging. Partial valid results are preserved.

### Use cases

- Build public prospect lists and qualify organizations or professionals before responsible outreach.
- Collect public content and engagement signals for research and reporting.
- Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
- Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
- Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

### Output example

```json
{
  "recordType": "Example recordType",
  "source": "Example source",
  "linkedinUrl": "Example linkedinUrl",
  "name": "Example name",
  "headline": "Example headline",
  "location": "Example location",
  "about": "Example about",
  "followers": 1,
  "companyId": "Example companyId",
  "employeeCount": 1,
  "industry": "Example industry",
  "website": "Example website"
}
```

The exact fields depend on the selected input and what the public source exposes. Use the dataset schema as the machine-readable contract and retain source URLs for verification.

### Run LinkedIn People & Company Lead Suite with the Apify API

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/linkedin-people-company-lead-suite').call({
  "personUrls": [],
  "companyUrls": [],
  "fallbackMode": "fallback",
  "maxResults": 25,
  "requestDelayMs": 1200
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

### Support

When reporting a problem, include the **Actor run ID**, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

### Frequently asked questions

#### Can I schedule LinkedIn People & Company Lead Suite?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

#### How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

#### How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

#### Can an AI agent call this Actor?

Yes. Add `muhammadafzal/linkedin-people-company-lead-suite` through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

# Actor input Schema

## `personUrls` (type: `array`):

Use this for public LinkedIn /in/ profile URLs, one per line. Example: https://www.linkedin.com/in/example/. Max 25 URLs. Do not provide login URLs or private identifiers.

## `companyUrls` (type: `array`):

Use this for public LinkedIn /company/ page URLs, one per line. Example: https://www.linkedin.com/company/shopify/. Max 25 URLs. Do not provide private or authenticated URLs.

## `fallbackMode` (type: `string`):

Use direct to parse public HTML only, fallback to use ScrapeCreators when direct extraction is blocked or empty, or providerOnly for authorized provider-backed extraction. The provider key must be configured as SCRAPECREATORS\_API\_KEY in the Actor environment.

## `maxResults` (type: `integer`):

Maximum total person and company records to return. Use 1 to 50. Defaults to 25.

## `requestDelayMs` (type: `integer`):

Respectful delay between direct LinkedIn requests. Use 500 to 10000 milliseconds. Defaults to 1200.

## Actor input object example

```json
{
  "personUrls": [],
  "companyUrls": [],
  "fallbackMode": "fallback",
  "maxResults": 25,
  "requestDelayMs": 1200
}
```

# Actor output Schema

## `dataset` (type: `string`):

Structured person and company lead records returned by the Actor.

## `summary` (type: `string`):

Delivery counts, access-path attempts, and warnings.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/linkedin-people-company-lead-suite").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/linkedin-people-company-lead-suite").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call muhammadafzal/linkedin-people-company-lead-suite --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammadafzal/linkedin-people-company-lead-suite"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/I5e2frVZnf9FssqJ3/builds/Ragcn1saW5M6v6nNF/openapi.json