# Post Engagement Scraper for LinkedIn - Commenters (`scrapesage/linkedin-post-engagement-scraper`) Actor

Turn the people who commented on LinkedIn posts into a lead list. One row per person, enriched from their own public profile with job title, company, seniority and location, and deduplicated across posts. No login.

- **URL**: https://apify.com/scrapesage/linkedin-post-engagement-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 engager founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Post Engagement Scraper for LinkedIn - Commenters

**The people who comment on a post are warm leads. This turns them into a list.** Give it post URLs, or a company/profile whose recent posts you want mined, and get **one row per person** - enriched from their own public profile with job title, seniority, department, current company and location, and deduplicated across posts so a repeat engager arrives once with `timesEngaged: 3`.

No login, no cookies.

### Why one row per person matters

A posts scraper gives you posts with comments nested inside them. That is the wrong shape for outreach: you cannot sort it, dedupe it, or push it into a CRM. This gives you the people.

### Input

| Field | What it does |
|---|---|
| `postUrls` | Exact posts to mine |
| `companyUrls` | Mine the recent posts of a company page |
| `profileUrls` | Mine the recent posts of a person |
| `enrichProfiles` | Open each commenter's profile for title, company, seniority, location (default on) |
| `dedupePeople` | One row per person with `timesEngaged` (default on) |
| `includeCompanyPages` | Include brand-account commenters (default off) |
| `maxPostsPerSource` / `maxCommentsPerPost` / `maxResults` | Caps |

### Output

```json
{
  "type": "engager",
  "fullName": "Jesse Davies",
  "profileUrl": "https://www.linkedin.com/in/jessevent",
  "jobTitle": "Head of Product",
  "seniorityLevel": "VP/Director",
  "department": "Product",
  "currentCompany": "Acme",
  "locationName": "Sydney, New South Wales, Australia",
  "commentText": "This is exactly the gap we hit last quarter...",
  "commentPostedAgoText": "2w",
  "timesEngaged": 2,
  "engagedPostUrls": ["https://www.linkedin.com/posts/...", "https://www.linkedin.com/posts/..."],
  "postUrl": "https://www.linkedin.com/posts/supabase_...",
  "postAuthorName": "Supabase",
  "isCompanyPage": false,
  "profileEnriched": true,
  "leadScore": 78
}
```

### What LinkedIn does and does not publish logged-out

Measured on this actor's own runs.

- **Commenters: yes.** Ten of ten carried a real profile URL on the test post, including country subdomains and brand accounts.
- **Reactions: NO - and nothing here pretends otherwise.** LinkedIn does not publish who *liked* a post to logged-out visitors: `/reactions` and `/likes` both return 404, the post page carries no reactor list, and `/recent-activity/reactions` answers 999. This actor returns commenters only. If a tool claims logged-out reaction lists, be sceptical.
- **Roughly the top ten comments per post** are published, not the full thread.
- **Some members switch their public profile off**, permanently answering 999. Those people still arrive (name, profile link, comment) with `profileEnriched: false` rather than being dropped.

### Pricing

Pay-per-event: **$0.005 per engager**. Runs that find nobody charge nothing.

### Use with AI assistants (MCP)

Works as a tool through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - "who engaged with our competitor's last ten posts, and what do they do?"

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** — AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

### Legal

Reads only what LinkedIn publishes to logged-out visitors; no login, no cookies, no private content. Commenter names and roles relate to identifiable people - in the EU/UK you are the data controller for the output, so have a lawful basis (usually legitimate interest for B2B) and honour deletion requests. Do not use it for spam.

Not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation.

# Actor input Schema

## `postUrls` (type: `array`):

LinkedIn post permalinks (https://www.linkedin.com/posts/...-activity-...). The most precise input when you already know the posts you care about.

## `companyUrls` (type: `array`):

Company pages whose recent posts should be read for engagement, e.g. https://www.linkedin.com/company/supabase or just the slug.

## `profileUrls` (type: `array`):

People whose recent posts should be read for engagement, e.g. a founder whose audience you want to reach.

## `enrichProfiles` (type: `boolean`):

Open every commenter's public profile to add job title, seniority, department, current company, location and follower count. Turning it off is much faster and cheaper but returns only the name, profile link and comment.

## `dedupePeople` (type: `boolean`):

Merge someone who commented on several of the posts into a single row with timesEngaged and the list of posts. Turn off to get one row per comment instead.

## `includeCompanyPages` (type: `boolean`):

Some comments come from brand accounts rather than people. Off by default so a lead list contains people; each row carries isCompanyPage either way.

## `maxPostsPerSource` (type: `integer`):

How many recent posts to read for each profile or company page you pass.

## `maxCommentsPerPost` (type: `integer`):

Cap per post. LinkedIn publishes roughly the top ten comments to logged-out visitors, so higher values rarely add more.

## `maxResults` (type: `integer`):

Total cap across every post. Set 0 for no limit (explicit opt-in).

## `maxConcurrency` (type: `integer`):

How many profiles to enrich in parallel.

## `proxyConfiguration` (type: `object`):

LinkedIn needs residential proxies for reliable logged-out access. Keep the default.

## `urlsFromFile` (type: `string`):

Paste a list of URLs (one per line), OR one link to a .txt/.csv file, Google Sheet or Google Drive file containing them. Lets you import many Start URLs at once instead of typing each. Google Sheet/Drive share links are handled automatically.

## Actor input object example

```json
{
  "postUrls": [
    "https://www.linkedin.com/posts/supabase_today-were-open-sourcing-supabase-evals-activity-7489047352075460608-EGgJ"
  ],
  "companyUrls": [
    "supabase"
  ],
  "profileUrls": [
    "https://www.linkedin.com/in/paulcopplestone"
  ],
  "enrichProfiles": true,
  "dedupePeople": true,
  "includeCompanyPages": false,
  "maxPostsPerSource": 10,
  "maxCommentsPerPost": 50,
  "maxResults": 100,
  "maxConcurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Every engager as a JSON item in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "postUrls": [],
    "companyUrls": [
        "supabase"
    ],
    "profileUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    },
    "urlsFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/linkedin-post-engagement-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "postUrls": [],
    "companyUrls": ["supabase"],
    "profileUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
    "urlsFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/linkedin-post-engagement-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "postUrls": [],
  "companyUrls": [
    "supabase"
  ],
  "profileUrls": [],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "urlsFromFile": ""
}' |
apify call scrapesage/linkedin-post-engagement-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/linkedin-post-engagement-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yI9RTDsBL1XlnhBUT/builds/XvvIKfjGHCw5R0TBF/openapi.json