LinkedIn Post Engagers Scraper avatar

LinkedIn Post Engagers Scraper

Pricing

from $0.01 / 1,000 engagers

Go to Apify Store
LinkedIn Post Engagers Scraper

LinkedIn Post Engagers Scraper

Collect public LinkedIn post engagers from the post URLs you submit. Filter by professional headline, omit profiles, and optionally add public company, location, follower count, and about details when available. No LinkedIn login or cookies are required.

Pricing

from $0.01 / 1,000 engagers

Rating

0.0

(0)

Developer

Maxime Dupré

Maxime Dupré

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

7 days ago

Last modified

Share

🎯 Find people engaging with LinkedIn posts

Sales teams, recruiters, and social media researchers can use this Actor to collect public LinkedIn post engagers from post URLs. It returns structured rows with a person's profile, available comment details, source-post context, and optional public profile enrichment. That gives you a clear list of people and the post activity that brought them into view.

Use cases

📊 See who engaged and what the post showed

Each saved dataset row keeps the person's public name and profile URL, the source post, and any comment or profile details that the public source provides. Enrichment is optional. Fields that are not available on the public source are omitted from the row.

Returned data

  • Person details: name, profile URL, and public professional headline when available.
  • Engagement details: public comment text and comment date when available.
  • Source-post context: URL, author, publication date, reaction count, comment count, and a short text preview when available.
  • Profile enrichment: current company, company page URL, location, follower count, and a short about preview when available.

▶️ Start with public post URLs

Run steps

  1. Add one or more public LinkedIn post URLs.
  2. Set an optional per-post result limit, profile enrichment choice, headline filters, or profile exclusions.
  3. Run the Actor and open the default dataset.

The same settings apply to every submitted post URL. Leave maxResultsPerPost empty to return all available results until the source is exhausted. The Actor uses public LinkedIn data and does not require a LinkedIn login or cookies.

⚙️ Input

The form uses one common configuration for all submitted post URLs.

Input fields

FieldTypeWhat it does
postUrlsarray of objects, requiredLists one or more public LinkedIn post URL objects to process.
postUrls[].urlstring, requiredThe public LinkedIn post URL to process. The form accepts /posts/ and /feed/update/ URLs.
maxResultsPerPostinteger, optionalSets the maximum number of engagers requested from each post. Leave it empty to return all available results until the source is exhausted.
includeProfileEnrichmentboolean, default trueAdds current company and public company page, location, follower count, and a short about preview when available. Core engagement results remain available when enrichment cannot be retrieved.
headlineIncludeKeywordsarray of strings, optionalKeeps people whose public professional headline contains at least one entered keyword. Leave it empty to keep all headlines.
headlineExcludeKeywordsarray of strings, optionalOmits people whose public professional headline contains at least one entered keyword. Leave it empty to exclude no headlines.
excludedProfileUrlsarray of strings, optionalOmits people with the public LinkedIn profile URLs you enter. Leave it empty to omit no profiles.

Default input example

This is the smallest common input from a successful current-beta run. It leaves maxResultsPerPost empty, so the Actor returns all available results until the source is exhausted.

{
"postUrls": [
{
"url": "https://www.linkedin.com/posts/ryanlflynn_only-connections-can-comment-on-this-post-activity-7325648430997876736-VYzA"
}
],
"includeProfileEnrichment": false
}

🧾 Output

The Actor provides a link to the default dataset. Core and enriched rows use the same public field names. Enriched rows add the optional profile fields shown in the second table.

Dataset link

FieldTypeWhat it does
datasetstringOpens the default dataset with the saved engagement rows.

Core engagement row

FieldTypeWhat it does
namestringPublic name shown for the person who engaged with the post.
profileUrlURL stringPublic LinkedIn profile URL for the person.
headlinestring, optionalPublic professional headline when available.
commentTextstring, optionalPublic comment text when available.
commentDateISO date-time string, optionalDate or time shown for the comment when available.
postobjectPublic source post connected to the engagement.
post.urlURL stringPublic LinkedIn URL of the source post.
post.authorobject, optionalPublic context for the source-post author.
post.author.namestring, optionalPublic name shown for the source-post author.
post.author.profileUrlURL string, optionalPublic LinkedIn profile URL for the source-post author.
post.publishedAtISO date-time string, optionalDate or time shown for the source post.
post.reactionCountinteger, optionalNumber of reactions shown for the source post.
post.commentCountinteger, optionalNumber of comments shown for the source post.
post.textPreviewstring, optionalShort preview of the source-post text.

This unshortened row is from a successful current-beta run with profile enrichment disabled.

{
"name": "Andre L.",
"profileUrl": "https://www.linkedin.com/in/alinde",
"commentText": "I have noticed this lately, seems like a strange gatekeeping for only allowing comments from people that they want to hear from.",
"commentDate": "2025-05-06T22:35:50.674Z",
"post": {
"url": "https://www.linkedin.com/posts/ryanlflynn_only-connections-can-comment-on-this-post-activity-7325648430997876736-VYzA",
"author": {
"name": "Ryan Flynn",
"profileUrl": "https://www.linkedin.com/in/ryanlflynn"
},
"publishedAt": "2025-05-06T22:31:29.886Z",
"reactionCount": 11,
"commentCount": 12,
"textPreview": "\"Only connections can comment on this post. You can still react or share it.\" Is this a new thing on LinkedIn?"
},
"headline": "Alinde Öst – Notyfile"
}

Enriched engagement row

FieldTypeWhat it does
namestringPublic name shown for the person who engaged with the post.
profileUrlURL stringPublic LinkedIn profile URL for the person.
headlinestring, optionalPublic professional headline when available.
commentTextstring, optionalPublic comment text when available.
commentDateISO date-time string, optionalDate or time shown for the comment when available.
postobjectPublic source post connected to the engagement.
post.urlURL stringPublic LinkedIn URL of the source post.
post.authorobject, optionalPublic context for the source-post author.
post.author.namestring, optionalPublic name shown for the source-post author.
post.author.profileUrlURL string, optionalPublic LinkedIn profile URL for the source-post author.
post.publishedAtISO date-time string, optionalDate or time shown for the source post.
post.reactionCountinteger, optionalNumber of reactions shown for the source post.
post.commentCountinteger, optionalNumber of comments shown for the source post.
post.textPreviewstring, optionalShort preview of the source-post text.
companyobject, optionalCurrent public company details when available.
company.namestring, optionalPublic name of the person's current company.
company.urlURL string, optionalPublic LinkedIn page URL for the person's current company.
locationstring, optionalPublic profile location.
followerCountinteger, optionalPublic follower count.
aboutstring, optionalShort preview of the person's public about section.

This unshortened row is from a successful current-beta run with profile enrichment enabled.

{
"name": "Jonathan Harrop",
"profileUrl": "https://www.linkedin.com/in/harropj",
"commentText": "I’m not NOT a fan, ya know?",
"commentDate": "2025-05-06T22:50:39.178Z",
"post": {
"url": "https://www.linkedin.com/posts/ryanlflynn_only-connections-can-comment-on-this-post-activity-7325648430997876736-VYzA",
"author": {
"name": "Ryan Flynn",
"profileUrl": "https://www.linkedin.com/in/ryanlflynn"
},
"publishedAt": "2025-05-06T22:31:29.886Z",
"reactionCount": 11,
"commentCount": 12,
"textPreview": "\"Only connections can comment on this post. You can still react or share it.\" Is this a new thing on LinkedIn?"
},
"headline": "Strategic Marketing & Communications ...",
"company": {
"name": "Citi",
"url": "https://www.linkedin.com/company/citi"
},
"location": "Dallas-Fort Worth Metroplex",
"followerCount": 5000,
"about": "As a mission-driven marketing leader, I bring a wealth of experience to the dynamic…"
}

💳 Pricing

This Actor uses pay-per-event pricing. The primary event is charged when a public engager is saved. Profile enrichment is a separate event and applies when public profile details are saved. Apify platform usage is separate from these Actor events. Actual event counts depend on what the public source exposes and which filters you use.

Machine eventPriceCharged when
linkedin-post-engager-found$0.00001One public LinkedIn engager is saved.
linkedin-post-engager-enriched$0.0108One saved engager has available public profile details.

🔌 Integrations

Use the Apify API or the default dataset to read the saved JSON rows. Review or export the dataset in Apify, and schedule repeat runs when you need refreshed public results.

❓ FAQ

What does an empty maximum do?

Leaving maxResultsPerPost empty returns all available results until the source is exhausted. Public availability can still produce fewer rows.

What happens if profile enrichment is unavailable?

Core engagement results remain available when profile enrichment cannot be retrieved. Fields such as company, location, follower count, and about text appear only when the public profile provides them.

How do the headline filters work?

The include list keeps a person when the public professional headline contains at least one entered keyword. The exclude list omits a person when the headline contains at least one entered keyword. An empty list leaves that filter unused.

Can I leave out known profiles?

Yes. Add their public LinkedIn profile URLs to excludedProfileUrls. Those profiles are omitted from the saved results.

Can I submit more than one post?

Yes. Add multiple public post URLs to postUrls. The same limit, enrichment choice, and filters apply to the whole list.

Will every public engager appear?

No. The Actor can return only data that the public source exposes at run time. Private, restricted, deleted, or otherwise unavailable activity may produce fewer results or none.

Do I need a LinkedIn login or cookies?

No. The Actor is designed for supported public post URLs and does not require customer-provided LinkedIn login details or cookies.

Does the output include private contact data?

No. The dataset documents public profile and post fields such as names, URLs, comments, company details, location, followers, and about text when available. It does not provide private email addresses, phone numbers, or private profile history.

📝 Changelog

v0.0 (25-09-2026)

  • Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

Made with ❤️ by Maxime Dupré