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

{
  "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

{
  "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

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.