Linkedin Company Employees Scraper avatar

Linkedin Company Employees Scraper

Pricing

$19.99/month + usage

Go to Apify Store
Linkedin Company Employees Scraper

Linkedin Company Employees Scraper

LinkedIn Company Employees Scraper extracts employee profiles from LinkedIn company pages. It collects names, job titles, profile URLs, locations, and profile details. Ideal for lead generation, recruitment research, B2B prospecting, and company workforce analysis.

Pricing

$19.99/month + usage

Rating

0.0

(0)

Developer

ScraperForge

ScraperForge

Maintained by Community

Actor stats

0

Bookmarked

8

Total users

0

Monthly active users

4 hours ago

Last modified

Share

Extract the people behind any company on LinkedIn — no login, no cookies, no LinkedIn account required. Drop in one or more company page URLs (or plain company names / keywords) and get back a clean, structured dataset of employee profiles: full names, headlines, locations, profile URLs, current company, profile pictures and more.

This LinkedIn company employees scraper is built for teams that need reliable, at-scale people data for lead generation, recruitment sourcing, sales prospecting, market research and B2B data enrichment — without the risk of sharing session cookies or getting an account flagged.

💬 Need a custom field, a higher volume plan, or a tailored LinkedIn data pipeline? Contact dev.scraperengine@gmail.com.


Why use this LinkedIn employees scraper

  • No cookies, no login required — nothing to expire, no account to burn.
  • 🔗 Bulk-friendly input — mix full company URLs and keyword/company-name discovery in a single run.
  • 👥 Per-company employee cap — pull anywhere from 1 to 10,000 employee profiles per company.
  • 🌐 Built-in residential proxy support — Apify Residential (US) is enabled by default to reduce blocks.
  • 📍 Geocoded locations — raw location strings are enriched into city, country and ISO country code.
  • 📊 Analyst-ready output — normalized, flat fields that export straight to CSV, JSON or Excel.

What data you get

Each employee record in your dataset contains the following fields (matching the actor's real output schema):

FieldTypeDescription
company_urlstringThe LinkedIn company page the employee was discovered from.
profile_urlstringCanonical public LinkedIn profile URL (/in/...).
fullnamestringFull display name of the person.
first_namestringParsed first name.
last_namestringParsed last / surname.
headlinestringLinkedIn headline / professional tagline.
public_identifierstringThe profile's public identifier (the /in/slug).
profile_picture_urlstringURL of the profile photo.
locationobjectStructured location: full, city, country, country_code (ISO).
current_companystringDetected current employer name.
companies_detectedarrayAll companies found on the profile (name, slug, url).
personal_websitestringFirst external (non-LinkedIn) website linked on the profile.
recommendations_receivedarrayRecommendation entries (text, author, author_url).
is_creatorbooleanCreator-mode flag.
is_influencerbooleanInfluencer flag.
is_premiumbooleanPremium account flag.
show_follower_countbooleanWhether follower count is public.
created_timestampintegerUnix timestamp of when the record was scraped.
other_contact_detailsobjectExtra contact signals (e.g. course_links).
contact_elementsobjectNested profile metadata (identity, learning content, platform links, languages).

ℹ️ Data is limited to what LinkedIn exposes publicly. Fields that aren't present on a given public profile are returned empty.


Key features

  • Company URL & keyword discovery — paste https://www.linkedin.com/company/google or just google; the actor resolves both.
  • Multi-source employee discovery — combines the company page (/people/, /about/) with public search to maximize coverage.
  • Configurable volumemax_employees lets you keep runs cheap (10 profiles for a quick test) or comprehensive (thousands).
  • Location enrichment / geocoding — turns messy location text into clean city + country + country code for regional segmentation.
  • Automatic name parsing — splits fullname into first_name and last_name for easy mail-merge and CRM import.
  • Resilient scraping — automatic retries, block detection and proxy rotation keep runs stable.
  • Flexible exports — download the dataset as CSV, JSON, Excel, or HTML, or pull it via the Apify API.

How to use it — step by step

  1. Add your targets. In the Company URLs or search keywords field, enter one entry per line — either full LinkedIn company URLs (e.g. https://www.linkedin.com/company/microsoft) or plain company names / keywords.
  2. Set the employee cap. Use Max employees per company (1–10,000, default 10) to control how many profiles to pull per target. Higher values = more data and longer runs.
  3. Configure the proxy (optional). Leave the default Apify Residential (US) proxy on for the fewest blocks, pick another country, or turn it off to send requests directly.
  4. Run the actor. Profiles stream into your dataset as they are scraped.
  5. Export the results. Download as CSV / JSON / Excel from the Storage tab, or fetch programmatically through the Apify API and integrations (Make, Zapier, n8n, Google Sheets).

Input example

{
"urls": [
"https://www.linkedin.com/company/google",
"https://www.linkedin.com/company/microsoft",
"stripe"
],
"max_employees": 50,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "US"
}
}
Input fieldRequiredDescription
urls✅ YesArray of LinkedIn company URLs and/or keywords (one per line).
max_employeesNoMax employee profiles per target (1–10,000, default 10).
proxyConfigurationNoProxy settings. Apify Residential (US) recommended.

Output example

{
"company_url": "https://www.linkedin.com/company/google",
"profile_url": "https://www.linkedin.com/in/jane-doe",
"fullname": "Jane Doe",
"first_name": "Jane",
"last_name": "Doe",
"headline": "Senior Software Engineer at Google",
"public_identifier": "/in/jane-doe",
"profile_picture_url": "https://media.licdn.com/dms/image/....jpg",
"location": {
"full": "Mountain View, California, United States",
"city": "Mountain View",
"country": "United States",
"country_code": "US"
},
"current_company": "Google",
"companies_detected": [
{ "name": "Google", "slug": "google", "url": "https://www.linkedin.com/company/google" }
],
"personal_website": "https://janedoe.dev",
"recommendations_received": [],
"is_creator": false,
"is_influencer": false,
"is_premium": false,
"show_follower_count": true,
"created_timestamp": 1751328000,
"other_contact_details": { "course_links": [] },
"contact_elements": { "...": "profile identity, learning content, platform & language metadata" }
}

Use cases

  • Lead generation & B2B prospecting — build targeted lists of decision-makers at your ICP companies.
  • Recruitment & talent sourcing — find engineers, sales reps or specialists working at competitor companies.
  • Sales intelligence & account mapping — see who works where and map org structures before outreach.
  • Market & competitor research — measure headcount, hiring trends and team composition across rivals.
  • CRM & data enrichment — append names, headlines, locations and profile links to existing records.
  • HR & workforce analytics — analyze talent distribution by location, seniority and function.

Frequently asked questions

Do I need a LinkedIn account or cookies? No. This scraper works entirely on publicly available data — no login, no session cookies, no account risk.

Can I search by company name instead of URL? Yes. Enter a plain company name or keyword and the actor will resolve it and discover matching employee profiles.

How many employees can I scrape per company? Anywhere from 1 to 10,000 via the max_employees setting. Larger caps mean longer runs and higher cost.

What data can I export? All fields listed above, downloadable as CSV, JSON, Excel or HTML, or accessible through the Apify API.

Why should I keep the proxy enabled? LinkedIn aggressively blocks datacenter traffic. Apify Residential proxies dramatically reduce blocks and improve success rates. Running without a proxy raises the chance of failed requests.

Are emails included? The scraper extracts public contact signals (personal website, external links, course links). Direct emails are only returned when a profile exposes them publicly.

Is this compliant with LinkedIn's terms? You are responsible for using scraped public data in line with applicable laws (including GDPR/CCPA) and LinkedIn's terms. Only collect and process data you are legally allowed to use.


LinkedIn company employees scraper · scrape LinkedIn employees no login · LinkedIn company page people extractor · LinkedIn lead generation scraper · LinkedIn recruitment sourcing tool · extract employees from LinkedIn company · LinkedIn profile scraper no cookies · B2B contact data scraper · LinkedIn employee database builder · bulk LinkedIn company scraper · LinkedIn sales prospecting data · export LinkedIn employees to CSV.