linkedin-reaction-scraper

LinkedIn Reaction Scraper

Pull every reactor from a LinkedIn post into a clean, deduped list - with a full LinkedIn profile attached to each row in one shot. Phase 1 of the reaction-to-outreach pipeline; also runnable standalone if you only need the list.

The big win over the commenter scrape: profileScraperMode: "main" makes the actor return the reactor's experience history, education, skills, certifications, location, and connections count directly. No second-pass enrichment for profile data needed (Apollo enrichment is still required for verified emails).

When to use

• "Scrape reactors from this LinkedIn post: ".
• "Pull a list of who reacted to this post, with their profiles".
• You want a clean, deduped reactor list with rich profile data for any downstream use.

When NOT to use

• You want commenters (lower volume, higher per-lead intent) - use linkedin-comment-scraper.
• You want the full end-to-end pipeline through to Instantly - use linkedin-reaction-to-outreach.

Connections I need

• Apify (scraping) - Required. I use the harvestapi/linkedin-post-reactions actor with profileScraperMode: "main".

If Apify isn't connected I stop and ask you to connect it from the Integrations tab.

Information I need

• The LinkedIn post URL - Required.
• A target item count - Optional. Defaults to defaultMaxItems from your outbound context (500). Reactor pulls regularly hit 500+ on a popular post; bump higher if you want full coverage of a viral post.

Steps

1. Validate URL. Same rules as the comment scraper: must be a LinkedIn post URL. Reject profile / article / company URLs. Resolve short links once.

2. Test pull. First call to the actor with maxItems: 20 and profileScraperMode: "main". Confirm shape includes experience, education, skills, connectionsCount. If those are missing, the actor wasn't given the right mode flag - fail loudly so you can see it.

3. Full pull. Call the actor with maxItems: {target} (default 500), profileScraperMode: "main". The reaction scrape with full profiles takes longer than the comment scrape - expect 5-15 minutes for 500 items.