LinkedIn Post Comments Scraper & Engaged Leads

Study public LinkedIn post discussions and discover people engaging with topics relevant to your market. Export comment text, author links, timestamps, and reply indicators without supplying LinkedIn cookies.

Quick start and cost

Start with postUrls with one public post URL, maxCommentsPerPost: 10, and dryRun: true for a preview. Dry runs return a sample record and do not collect live platform data. For a real run, turn off dryRun and use a small input limit first. This Actor calls a separately priced source Actor for live collection. Its published per-result price and source-Actor usage are distinct; check your Apify usage and the source-cost cap before scaling. Private, deleted, restricted, or changed pages can return fewer records than requested.

Best use cases

• engaged lead discovery
• social selling research
• comment sentiment research
• event prospecting
• influencer audience analysis

What you get

• commentText
• authorName
• authorHeadline
• authorUrl
• postedAt
• reactionCount
• likeCount
• isReply
• postUrl
• commentUrl
• sourceActorRunId for troubleshooting and traceability
• raw containing the complete source item when you need extra fields

Example input

{
  "postUrls": [
    "https://www.linkedin.com/posts/example/"
  ],
  "maxCommentsPerPost": 25,
  "includeReplies": false
}

Example output

{
  "commentText": "This is a useful update.",
  "authorName": "Example Person",
  "authorHeadline": "VP Sales at Example",
  "authorUrl": "https://www.linkedin.com/in/example/",
  "postedAt": "2026-08-20T12:00:00Z",
  "likeCount": 8,
  "isReply": false
}

How it works

1. Enter the specific URLs, names, or usernames supported by this Actor.
2. The Actor validates and deduplicates your input.
3. A maintained no-cookie source Actor collects the live public data.
4. Results are normalized into consistent fields and duplicate records are removed.
5. Download the dataset as JSON, CSV, Excel, XML, or RSS, or connect it to your workflow through the Apify API.

Pricing and cost control

This Actor uses pay-per-result pricing. You are charged for unique records saved to this Actor's dataset. Store discounts are applied automatically by Apify for higher subscription tiers.

The advanced source cost limit is automatically calculated from your requested item limits. Set sourceMaxTotalChargeUsd only when you need a stricter custom cap. A source run can still return zero records when a URL is invalid, private, removed, or has no matching public content.

Reliability notes

• No LinkedIn or Instagram cookie is requested from you.
• Duplicate inputs and duplicate result records are removed.
• Invalid URLs fail early with a clear message.
• The raw source item is retained so downstream integrations do not lose uncommon fields.
• Public platform pages and schemas can change. Failed source runs are surfaced with their run ID for debugging.

Responsible use

Only collect publicly available data that you are legally permitted to process. Follow applicable privacy, data protection, anti-spam, copyright, and platform rules. Do not use this Actor for harassment, unlawful profiling, credential collection, or abusive automation.

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn, Instagram, Meta, or Microsoft. Product names and trademarks belong to their respective owners.

Workflow and operating limits

Discussion research: provide a known public post URL, sample comments, and classify recurring questions or sentiment downstream. Replies depend on the input option and source availability.

Limits and result interpretation

Comment availability and ordering depend on LinkedIn and the collection source. Empty or restricted discussions are not guaranteed to return data. Source error records are not charged as successful comments.

Result price versus total workflow cost

Base pricing is $4 per 1,000 saved comments plus separately billed collection source charges. Begin with maxCommentsPerPost: 1 and inspect the total workflow cost before increasing the limit.

Actor-start charges may apply even if no paid result is saved. Verify current prices in the Pricing tab; discounts depend on your plan. Budget settings cap charges rather than guaranteeing a quantity of results.

API and n8n workflow

Use the Console API menu to generate the run request for this Actor. Keep your Apify token in a credential, not in a public URL or shared workflow. In n8n, start a run with HTTP Request or the Apify integration, poll until it ends, then download the default dataset as JSON or CSV. Check status fields and error rows before importing data; SUCCEEDED alone does not prove that live data was collected.

The Run status / preview output link points to the OUTPUT record. A preview is never evidence that the upstream source is working.

Troubleshooting and support

Start with one valid public input. Check Runs, the run status and Logs, then inspect the dataset. If a paid source is used, inspect its run separately. Account concurrency limits can temporarily prevent a child run from starting; submit batches sequentially on small plans. Report the run ID and a redacted input through this Actor's Issues tab. Never post tokens, LinkedIn cookies, or other session credentials. Share a customer run only through Apify's supported opt-in sharing controls.