linkedin-scrape

Find LinkedIn profiles, posts, companies, and people via LinkedIn MCP or Apify actors.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/alectivism/organization-ai-skills --skill linkedin-scrape-alectivism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linkedin-scrape
Source: https://github.com/alectivism/organization-ai-skills/tree/main/org-research/skills/linkedin-scrape
Command: npx skills add https://github.com/alectivism/organization-ai-skills --skill linkedin-scrape-alectivism

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Researching LinkedIn profiles, posts, and companies manually is slow and error-prone, and choosing the wrong scraping method risks wrong-company matches, wasted billed records, or personal-session exposure. ## Core Features & Use Cases - LinkedIn MCP for small batches: Look up person profiles, posts, and people/company search through the LinkedIn MCP with serialized, paced requests. - Apify for volume and enrichment: Run Apify actors for high-volume or recurring batches, verified email/phone enrichment, and exact company-URL employee searches without a personal LinkedIn session. - Use Case: A recruiter needs verified emails for 200 candidates at a target company. The skill routes the work to the Apify company-employees and profile-scraper actors, fetching current input schemas before each run and retrieving only needed fields. ## Quick Start Find the LinkedIn profile and recent posts for this person, and use Apify if you need verified contact details for a large list.

Frequently Asked Questions about linkedin-scrape

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scrape LinkedIn profiles and posts?▼

Use the LinkedIn MCP get_person_profile tool for individual profiles and posts, requesting the posts section only when needed. For bulk profile scraping, use the Apify harvestapi/linkedin-profile-scraper actor after fetching its current input schema.

LinkedIn MCP vs Apify for LinkedIn scraping?▼

Use the LinkedIn MCP for normal small-batch research like single profiles and searches. Use Apify for high-volume or recurring batches, verified email/phone enrichment, exact company-URL employee searches, or work that must avoid a personal LinkedIn session.

How do I get verified emails from LinkedIn profiles?▼

Use the Apify harvestapi/linkedin-profile-scraper actor for a profile with verified email, or dev_fusion/Linkedin-Profile-Scraper for both email and phone. Fetch the actor's current input schema before every run since fields change.

Why does LinkedIn company lookup return the wrong company?▼

Name-only lookup can resolve to the wrong company. Search or verify the exact vanity slug from the LinkedIn URL's final path segment before reading the company's profile, posts, or employees.

What are the limitations of LinkedIn scraping with Apify?▼

Actor fields and enum values change, so static JSON examples break; always fetch the current input schema first. Reactions and comments on posts add billed result records, and some runs return an approval URL that must be approved before retrying.