See llms.txt for all machine-readable content.
Open a role in a form and get a scored candidate shortlist in Slack. It maps your competitors' teams on LinkedIn, searches the role in your city, reads each public profile, and has AI score everyone against your job description, quoting the profile. Every candidate lands in Google Sheets.
peoplePerCompany sets how deep each competitor team is mapped; five is plenty for a first shortlistshortlistScore and shortlistSize decide who reaches Slack, without touching the promptmaxCandidates caps how many people are scored, which caps the model costHow do I find candidates on competitor teams without LinkedIn Recruiter? This template builds a talent map from public LinkedIn pages. One Actor lists the people at each competitor whose public profile mentions your title in your city, and opens each profile to confirm they work there today. A second Actor runs a plain LinkedIn people search for the same title. Nothing uses your LinkedIn account or a cookie.
How is the AI score kept honest? The model only sees a short card built from the person's public data, and it has to quote the phrase that backs its score. A Code node checks that the quote is really on the card. A high score with a quote that isn't there goes to Check by hand instead of the shortlist, and the Notes column says why.
Why does the shortlist sometimes include fewer people than I asked for? The competitor search matches your title anywhere on a public profile, so a search for product designer can also return an engineer whose profile mentions the design team. Those people score low against the job description and stay off the shortlist. The run never pads the list, and a role with nobody above the cut-off gets a Slack message naming the three closest people and their gaps.
What happens when a competitor returns nobody? Some companies have few public profiles that match a title in one city. The first row in the sheet notes every competitor that came back empty. If both searches find nobody, one row is still logged with the reason, and Slack suggests widening the title or the location.
What does it cost? Five competitors at five people each costs about 13 cents in Apify charges, plus one small model call per candidate. Each confirmed competitor employee is $0.005, each search result is $0.0006, and each profile read is a fraction of a cent. A run takes five to ten minutes, most of it in the competitor search.
What else can these Actors do? LinkedIn Company Employees API lists the people who work at up to 50 companies per run, filtered by title and location. That makes it useful for talent mapping, account mapping and CRM hygiene. LinkedIn People Search API is a LinkedIn people search by name, title, company, school or place, and works as a recruiter alternative for finding profiles. LinkedIn Profile API returns public profile data for up to 1,000 URLs per run. If you self-host n8n, n8n-nodes-linkedin-company-employees-api and n8n-nodes-linkedin-profile-api wrap two of them as community nodes.
About Apify. LinkedIn Company Employees API runs on Apify, a platform of ready-made scrapers and APIs for sources that have no usable public API. Actors are pay per use with no subscription, and they run in the cloud, so nothing runs on your machine and nothing breaks when the source changes its markup.
New to Apify? You can set up a free account and get the API token this template needs in a couple of minutes.