LinkedIn Leads Scraper: Post Engagers, Comments & Reactions avatar

LinkedIn Leads Scraper: Post Engagers, Comments & Reactions

Pricing

Pay per event

Go to Apify Store
LinkedIn Leads Scraper: Post Engagers, Comments & Reactions

LinkedIn Leads Scraper: Post Engagers, Comments & Reactions

Scrape LinkedIn post likers and commenters into leads: export everyone who reacted or commented on any LinkedIn post, deduped across posts, filtered by job-title keywords. One lead per ICP match with the engagement signal. No LinkedIn login or cookies. Filtered-out engagers are never charged.

Pricing

Pay per event

Rating

0.0

(0)

Developer

George Kioko

George Kioko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Share

No cookies. No login. No LinkedIn account of yours involved. Cookie-based engagement tools run through your own LinkedIn session and put your account at risk; this actor reads public engagement through established scrapers running under your Apify account instead. You are charged per ICP-matched lead only. Duplicates, suppressed profiles, and engagers your filters reject are never charged as leads.

LinkedIn Leads Scraper is an Apify Actor that collects everyone who commented on or reacted to any LinkedIn post, dedupes them across posts, filters them against your ideal-customer rules, and returns one structured lead row per matching person — including their comment text or reaction type as the outreach signal. It is a LinkedIn post engagers scraper and LinkedIn lead generation tool built on real intent: everyone who engages with a post in your niche is raising their hand about that topic.

✅ Commenters + all reaction types · ✅ Dedupe across posts + suppression list · ✅ ICP filter on headline keywords · ✅ Pay only for matched leads · ✅ MCP ready for AI agents

Pricing — the honest version

EventPriceYou pay when
Actor startshown on the Pricing tabOnce per run
ICP-matched lead$0.005Per deduped, filter-matched lead row

$5 per 1,000 matched leads, plus the one-time start fee. A 1,000-engager post with a 20% match rate produces about $1 in lead charges. Two honest notes:

  • The raw engagement scrape runs under your account through established engagement scrapers (~$2 per 1,000 engagers, billed by them, for all engagers scraped). The ICP filter saves you money on leads, not on the scrape — cap it with maxEngagersPerPost.
  • Duplicates, suppressed profiles, and non-matching engagers are never charged by this actor. Runs that produce nothing produce no lead charges; upstream failures become a free usage row that says exactly what happened.

How it works

LinkedIn post URLs (yours or any influencer's)
commenters + reactions collected via proven
engagement scrapers, run under YOUR account
dedupe across posts + your suppression list
(someone who commented AND reacted = one lead,
the comment row wins — it has text)
ICP filter on headline keywords (free data)
│ match │ no match
▼ ▼
charged `lead` row dropped, never
($0.005 each) charged
free `post-summary` row per post
(engagers found, unique, matched, charged)

What data does it extract?

lead — one per ICP-matched engager:

FieldExample
nameJane Doe
headlineHead of Growth Marketing at Acme
profileUrlhttps://www.linkedin.com/in/jane-doe
engagementTypecomment
commentTextWe tried exactly this last quarter — the attribution part is the hard bit.
reactionTypeINSIGHTFUL (reaction rows)
engagedAt2026-08-10T05:31:58Z
postUrlthe post they engaged with
billabletrue

post-summary — one per post, always free: engagersFound, uniquePeople, duplicates, suppressed, icpMatched, charged.

What is NOT returned

  • ❌ Emails — v1 deliberately ships without email enrichment; pipe the profile URLs into Clay, Apollo, or your waterfall stack
  • ❌ Phone numbers
  • ❌ Full profile data (work history, education) — you get name, headline, profile URL, and the engagement signal
  • ❌ Private or logged-in-only engagement — only publicly visible commenters and reactions

Quick start

  1. Paste one or more LinkedIn post URLs (https://www.linkedin.com/posts/... or /feed/update/...).
  2. Set your ICP: titleIncludeKeywords (e.g. founder, marketing, growth), titleExcludeKeywords (e.g. student, intern), and optionally a suppressionList of profile URLs already in your CRM.
  3. Run it. Export JSON/CSV/Excel, or wire the dataset into Clay, Instantly, HeyReach, n8n, or your own pipeline via the API.
{
"postUrls": ["https://www.linkedin.com/posts/example-influencer_activity-12345"],
"titleIncludeKeywords": ["founder", "growth", "marketing"],
"titleExcludeKeywords": ["student", "intern"],
"maxEngagersPerPost": 1000
}

Use cases

  1. Signal-based outbound — instead of cold lists, mail people who just engaged with your topic. The commentText field is your personalized opening line.
  2. Competitor audience capture — run it on a competitor's product announcements; everyone reacting is in-market.
  3. Influencer audience mining — monitor the 5–10 creators your buyers follow and turn every new post's engagers into a deduped lead stream (pair with the Apify scheduler).
  4. Event & launch follow-up — posts about a conference or launch collect exactly the people you want at the top of your funnel.

Use from Claude, ChatGPT and any MCP agent

Add this actor to any MCP client (Claude, Cursor, ChatGPT) through the Apify MCP server:

https://mcp.apify.com/?tools=george.the.developer/linkedin-post-engagers-scraper

Or call it programmatically:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('george.the.developer/linkedin-post-engagers-scraper').call({
postUrls: ['https://www.linkedin.com/posts/example-influencer_activity-12345'],
titleIncludeKeywords: ['founder', 'growth'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
// lead rows: { name, headline, profileUrl, engagementType, commentText, ... }

Integrations

  • Clay — add a Import data from API source with your run's dataset URL: https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&format=json&clean=1, then map profileUrl into your enrichment table.
  • n8n — add the Apify node → operation Run Actor and Get Dataset Items → this actor → feed profileUrl + commentText into your outreach workflow.
  • Make / Zapier — Apify app → Run Actor module → Get Dataset Items.
  • Instantly / HeyReach / CRM — export CSV/Excel from the run, or pull the dataset URL above on a schedule.

FAQ

Where do emails come from?

They don't — v1 deliberately ships without email enrichment. You get clean profile URLs plus the engagement signal; pipe them into your existing enrichment stack (Clay, Apollo, waterfall tools).

It collects only publicly visible engagement data via established scrapers, with no login and no cookies. What you do with the leads is subject to your local outreach laws — that part is on you.

Why do I also see charges from another scraper?

That's the underlying engagement scrape running under your account (see Pricing). This actor's own charges are only the start fee and matched leads.

Someone engaged twice — do I pay twice?

No. Comments are processed first, reactions second; the same person across both (or across multiple posts in one run) is one lead.

Can I keep it running on new posts automatically?

Yes — put the actor on an Apify schedule and keep your suppression list topped up with already-contacted profiles; only new matches cost you anything.

How do I scrape LinkedIn post commenters?

Paste the post URL, keep includeComments on, run. Every commenter comes back with name, headline, profile URL, and their comment text.

How do I extract people who liked a LinkedIn post?

Same run — includeReactions collects everyone who reacted (like, celebrate, insightful, love) with the reaction type on each row.

Does this work for LinkedIn lead generation without Sales Navigator?

Yes. It reads public post engagement — no Sales Navigator, no LinkedIn account, no browser extension.

Can I export LinkedIn post engagers to CSV or Excel?

Yes — every run's dataset exports as CSV, Excel, JSON, or XML from the Apify Console or API, ready for Clay, Instantly, HeyReach, n8n, or your CRM.