n8n-nodes-linkedin-company-employees-api

An n8n community node that lists the people who work at a company, from LinkedIn's public pages: name, job title, location, and profile URL, with each person checked against their public profile to confirm they still work there. Give it LinkedIn company URLs or company names, and narrow the list by job title and location. It is backed by the LinkedIn Company Employees API on Apify and bills per person returned, so there are no subscriptions and no minimums. No LinkedIn account, login, or cookie is needed.

Installation · Credentials · Operations · Output · Example workflows · Pricing · Resources

What it does

Give the node one or more companies, and it returns one item per person who works there. All the companies on one input item are collected in a single Actor run. It also works as an AI Agent tool, so an agent can look up who works where on demand.

• Build a company employee list from a LinkedIn company URL or just the company name
• Narrow to the roles you care about with job title keywords ("head of", "engineer", "recruiter") and locations
• Confirm current employment: each person's public profile is opened and checked for a current role at the company, so people who left are not returned
• Get the full public profile for verified people: about text, work history, education, follower count
• Handle up to 50 companies and up to 1,000 people per company in one run
• Choose how much data to return per person: Simplified, Raw, or Selected Fields

Typical uses: account-based prospecting (list the decision makers at your target accounts), recruiting and talent mapping (see who is on a competitor's team, and where), team maps (how many engineers, designers or recruiters a company shows publicly, and where they sit), and CRM hygiene (check that your contacts still work at the account).

Installation

Follow the n8n community nodes installation guide:

1. In n8n, open Settings > Community Nodes.
2. Select Install.
3. Enter n8n-nodes-linkedin-company-employees-api as the npm package name.
4. Agree to the risks of using community nodes, then select Install.

After it installs, the LinkedIn Company Employees node appears in the nodes panel.

n8n Cloud only allows verified community nodes, so install this node on a self-hosted n8n instance.

Credentials

You need a free Apify account and an API token.

1. Sign in to the Apify Console.
2. Open Settings > Integrations and copy your Personal API token.
3. In n8n, create a new Apify API credential and paste the token.
4. Use the credential's Test button to confirm it works.

The node also supports Apify OAuth2 if you prefer to connect that way.

Operations

Employee > Get Many lists the people who work at one or more companies and returns one item per person.

Coverage: what to expect

The API finds people through public search results and then checks them against LinkedIn, so it returns the people search engines have indexed, not a company's full headcount. Smaller companies get the highest coverage. For a company with tens of thousands of employees, expect hundreds of people, not thousands: add Job Title Keywords and Locations to get the slice you need, or raise Max Search Slices per Company. Each run also writes a RUN_SUMMARY record with the coverage per company to the run's key-value store on Apify (it is not part of the node's output).

Output

Each person is returned as its own n8n item. A company that cannot be matched or searched returns one item with result_type set to error (never charged), so you can see which inputs to fix. The API returns more than ten fields per person, so the Output parameter lets you choose how much to return:

• Simplified (default): a compact object with result_type, fullName, currentTitle, headline, companyName, location, verified, and profileUrl. For an error item it returns result_type, requestedCompany, error_type, and error_message. This mode is also used automatically when the node runs as an AI Agent tool, to keep responses small.
• Raw: every field the API returns for each person, using the original field names below.
• Selected Fields: pick exactly which fields to include.

A Simplified item looks like this (synthetic example):

{
  "result_type": "employee",
  "fullName": "Sam Sample",
  "currentTitle": "Senior Software Engineer",
  "headline": "Senior Software Engineer at Example Co",
  "companyName": "Example Co",
  "location": "Dublin, Ireland",
  "verified": true,
  "profileUrl": "https://www.linkedin.com/in/sam-sample-0000"
}

Fields (Raw and Selected Fields)

Email addresses and phone numbers are not on LinkedIn's public pages, so the node does not return them.

Example workflows

1. Map the decision makers at your target accounts

1. Google Sheets: read your target account list (one company URL or name per row).
2. LinkedIn Company Employees: Companies {{ $json.company }}, Job Title Keywords head of, director, vp, Max Employees per Company 25.
3. Google Sheets or your CRM node: append fullName, currentTitle, companyName, location, and profileUrl for each person.

2. Map a competitor's team for recruiting

1. Manual Trigger.
2. LinkedIn Company Employees: add the competitor's LinkedIn URL, Job Title Keywords data engineer, Locations Dublin, Output Selected Fields with fullName, currentTitle, location, positions, education, and profileUrl.
3. Airtable: create one record per person for your sourcing pipeline.

3. Confirm your CRM contacts still work at their accounts each month

1. Schedule Trigger: once a month.
2. LinkedIn Company Employees: the accounts you track, Output Selected Fields with slug, fullName, currentTitle, and profileUrl.
3. Compare Datasets: match this month's people against your CRM contacts on slug.
4. Slack: post the contacts confirmed as current, and the people newly seen at each account. Treat a contact who does not appear as "not seen this run", not as "left": the list is partial, and a person can still work there without showing up in public search.

4. Let an AI Agent look up a team

1. AI Agent node.
2. Attach LinkedIn Company Employees as a tool.
3. Ask "Who are the engineering leaders at linkedin.com/company/stripe in Dublin?" The agent calls the node (in Simplified mode) and answers from the returned people.

Pricing

This node calls the LinkedIn Company Employees API on Apify, which is billed pay-per-event with no subscription and no minimums. You pay per person returned, never per search: a verified person (profile confirms a current role) or a found person (search-level row, when Verify Employment is off or a profile could not be opened), never both for the same person. Each run also carries a small start event, and each stored row a small dataset-item event. Error rows are never charged as a person, and people dropped as former employees produce no row and no charge. Apify's free plan includes monthly platform credits for trying it out. See the Actor page for current rates.

Related nodes

Part of a suite of LinkedIn APIs for n8n that read only LinkedIn's public pages, with no login and no cookies:

• n8n-nodes-linkedin-company-api: company firmographics (size, industry, headquarters, followers)
• n8n-nodes-linkedin-profile-api: full public profiles from profile URLs
• n8n-nodes-linkedin-jobs-api: the roles a company is hiring for
• n8n-nodes-linkedin-posts-api: posts from profiles and companies

Resources

• LinkedIn Company Employees API on Apify
• npm package
• Python and MCP example repo
• Source page on Alpha OSINT
• n8n community nodes documentation
• Apify n8n integration guide

License

MIT