LinkedIn Employee Scraper: Company People & B2B Lead Extractor

Extract LinkedIn employee profiles from company people search using your own authenticated LinkedIn session cookies. This Actor helps sales teams, recruiters, growth teams, founders, and data teams build targeted employee lists for B2B prospecting, recruiting research, account mapping, and market intelligence.

This Actor is unofficial and is not affiliated with LinkedIn.

What you can extract

• Employee name
• Current job title or headline
• Location
• LinkedIn profile URL
• Source company URL
• Matched role, keyword, or tag
• Search mode and scrape timestamp

Popular use cases

• Build B2B lead lists from a target company
• Find software engineers, founders, HR managers, recruiters, sales leaders, marketers, or decision makers
• Map employees at a competitor or target account
• Export company people search results to JSON, CSV, Excel, Google Sheets, CRM, n8n, Make, or Zapier
• Collect role-based LinkedIn profile URLs for enrichment workflows

Why use this Actor

• Uses authenticated LinkedIn requests with your own li_at and JSESSIONID cookies
• No browser automation, Selenium, or Puppeteer required
• Supports multiple company URLs and multiple role keywords in one run
• Supports title search for targeted roles and keyword search for broader discovery
• Supports optional geographic filtering with LinkedIn geo URNs
• Outputs clean structured records in the default Apify dataset

Input

Field	Description
Company URLs	LinkedIn company page URLs, for example https://www.linkedin.com/company/google
Keywords / Job Titles	Roles or search terms, for example software engineer, founder, marketing manager
li_at Cookie	Your LinkedIn session cookie. Stored as a secret input field.
JSESSIONID Cookie	Your LinkedIn CSRF/session cookie. Stored as a secret input field.
Search Mode	Use title for strict job title search or keywords for broader matching.
Max Pages per Tag	Number of LinkedIn result pages to process per keyword. Each page is about 10 results.
Max Profiles per Company	Optional safety limit for saved unique profiles per company. Use 0 for no limit.
Geo URN	Optional LinkedIn location filter, for example India.

Quick start

1. Enter one company URL, one specific title, and both fresh session cookies in the required secret fields.
2. Start with maxPages: 1 and maxProfilesPerCompany: 10.
3. Inspect the returned profile URLs before increasing the limits.

Missing, expired or placeholder sessions produce an actionable warning and no saved profiles. Network failures, rate limiting and extraction errors remain visible; retries cannot guarantee access to LinkedIn. Never place cookies in public tasks, issue reports, or shared datasets.

Example input

{
  "dryRun": false,
  "companyUrls": [
    "https://www.linkedin.com/company/google"
  ],
  "tags": [
    "software engineer",
    "product manager"
  ],
  "searchMode": "title",
  "maxPages": 5,
  "maxProfilesPerCompany": 100,
  "delay": 2
}

Add your own li_at and jsessionid values in the secure input fields before running.

Output example

{
  "name": "Jane Doe",
  "designation": "Software Engineer at Google",
  "location": "San Francisco Bay Area",
  "profileUrl": "https://www.linkedin.com/in/example/",
  "company_name": "Google",
  "input_company_url": "https://www.linkedin.com/company/google",
  "tag": "software engineer",
  "search_mode": "title",
  "scraped_at": "2026-08-24T00:00:00.000Z"
}

Tips for better results

• Use specific role titles such as founder, head of sales, recruiter, software engineer, or marketing manager.
• Use title mode when you need accurate role-based results.
• Use keywords mode when you want broader discovery across profile text.
• Start with maxPages set to 1-5, then increase after checking output quality.
• Use maxProfilesPerCompany to control spend on large company pages.
• Use a small delay to reduce rate limiting risk.

Cookie requirements

This Actor requires your own LinkedIn session cookies because it extracts data from authenticated LinkedIn people search views. Your cookie inputs are marked as secret in the input schema.

Legal and platform note

Use this Actor responsibly and only for lawful purposes. Review LinkedIn terms and applicable privacy/data protection rules for your use case. This Actor is unofficial and not affiliated with LinkedIn.

Required LinkedIn session inputs

A live extraction requires both li_at and jsessionid. Enter only your own current LinkedIn cookie values in the secret input fields. The Actor cannot run a live search without them. Cookies can expire or be revoked by LinkedIn, so replace them when an authentication error occurs. Never place cookie values in public tasks, issue reports, or shared datasets.

Workflow and operating limits

Account mapping and recruiting research: select one company and one specific role, use maxPages: 1 and a small maxProfilesPerCompany, then inspect the returned profile URLs before expanding.

Limits and result interpretation

Live extraction requires both current li_at and jsessionid from your own authorized LinkedIn session. Cookies may expire or hit LinkedIn restrictions. Preview writes only an OUTPUT record, not a dataset or employee-profile charge, and is not a live extraction or a reliability test. Authentication-dependent Store test exemption must be arranged with Apify; sample data is not a substitute.

Result price versus total workflow cost

Base pricing is $3 per 1,000 saved employee profiles, with plan discounts shown in Pricing. Preview and input/authentication warnings save no paid profiles; a small Actor-start charge can still apply. Genuine network or extraction errors remain visible.

Actor-start charges may apply even if no paid result is saved. Verify current prices in the Pricing tab; discounts depend on your plan. Budget settings cap charges rather than guaranteeing a quantity of results.

API and n8n workflow

Use the Console API menu to generate the run request for this Actor. Keep your Apify token in a credential, not in a public URL or shared workflow. In n8n, start a run with HTTP Request or the Apify integration, poll until it ends, then download the default dataset as JSON or CSV. Check status fields and error rows before importing data; SUCCEEDED alone does not prove that live data was collected.

The Run status / preview output link points to the OUTPUT record. A preview is never evidence that the upstream source is working.

Troubleshooting and support

Start with one valid public input. Check Runs, the run status and Logs, then inspect the dataset. If a paid source is used, inspect its run separately. Account concurrency limits can temporarily prevent a child run from starting; submit batches sequentially on small plans. Report the run ID and a redacted input through this Actor's Issues tab. Never post tokens, LinkedIn cookies, or other session credentials. Share a customer run only through Apify's supported opt-in sharing controls.