LinkedIn Profile Reactions
Pricing
$2.00 / 1,000 profile reaction results
LinkedIn Profile Reactions
Extract posts reacted to by public LinkedIn profiles, including action labels, post text, authors, timestamps, engagement counts, reaction breakdowns, attachments, and shared-post context. Batch up to 1,000 profiles and export JSON, CSV, or Excel—no LinkedIn cookies or login required.
Pricing
$2.00 / 1,000 profile reaction results
Rating
0.0
(0)
Developer
Data Slayer
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 hours ago
Last modified
Categories
Share
Give it one or more public LinkedIn profile URLs and get structured records of the posts those profiles reacted to — post text, author, engagement counts, full reaction breakdown, and attachments — with no LinkedIn cookies or login credentials.
Cookieless · Fresh data · No LinkedIn login or account risk.
Watch the demo
Video tutorial coming soon.
What you get
Each dataset item is one unique reacted-to post for one input profile:
- the reacting profile's URL, public identifier, and name, plus the public action label (e.g.
Satya Nadella likes this) - the reacted-to post's URL, URN, full text, publication time, and repost/edited flags
- aggregate engagement on the post: total reactions, comment count, share count, per-type counts (Like, Praise, Empathy, Appreciation, Interest, Entertainment), and a
reaction_breakdownarray - the post author's name, headline, LinkedIn URL, and image URL
- attachments, mentions, and shared-post context when available
input_index,reaction_index, andfetched_atfor stable ordering and traceability
Output example
{"reaction_id": "9b2f49c47228405419cebf6120a9f10613a0279cfd71e664bc4201a56fae441b","reacting_profile_url": "https://www.linkedin.com/in/satyanadella","reacting_profile_identifier": "satyanadella","reacting_profile_name": "Satya Nadella","reaction_action": "Satya Nadella likes this","reaction_target": "Post","post_id": "7481741318122110976","post_url": "https://www.linkedin.com/posts/bradsmi_a250-ugcPost-7481741318122110976-ImDL","post_text": "To coincide with the #A250, Microsoft unveiled an AI experience...","post_created_at": "2026-07-12T00:13:45.784Z","post_is_repost": false,"post_is_edited": false,"total_reaction_count": 960,"post_comment_count": 84,"post_share_count": 90,"like_reaction_count": 795,"praise_reaction_count": 41,"empathy_reaction_count": 87,"reaction_breakdown": [{"reaction_type": "LIKE", "count": 795},{"reaction_type": "EMPATHY", "count": 87},{"reaction_type": "INTEREST", "count": 26},{"reaction_type": "PRAISE", "count": 41}],"post_author_name": "Brad Smith","post_author_headline": "Vice Chair and President at Microsoft Corporation","post_author_linkedin_url": "https://www.linkedin.com/in/bradsmi","attachments": [],"mentions": [],"input_index": 0,"reaction_index": 0,"fetched_at": "2026-07-13T00:00:00.000Z"}
For CSV and spreadsheet exports, scalar fields stay as columns; reaction_breakdown, attachments, mentions, and shared_post export as compact JSON cells. IDs stay strings to prevent precision loss.
Input
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
profile_urls | array of strings | Yes | — | Between 1 and 1,000 public linkedin.com/in/... profile URLs. Regional LinkedIn hosts are accepted. |
max_reactions_per_profile | integer | No | 100 | Save between 0 and 1,000 unique records per profile. 0 continues until pagination ends or the 100-page cap is reached. |
posted_within | string | No | any | Keep posts published within 24h, week, month, 3months, 6months, year, or use any. |
Example:
{"profile_urls": ["https://www.linkedin.com/in/satyanadella"],"max_reactions_per_profile": 100,"posted_within": "any"}
Company pages, post URLs, search pages, Sales Navigator links, and bare profile identifiers without the full URL are rejected before any extraction request.
How to use it
- Copy one or more public LinkedIn profile URLs (up to 1,000 per run).
- Paste them into LinkedIn Profile URLs.
- Optionally set a per-profile limit and a post-age filter.
- Click Start.
- Open the dataset to inspect or export the reaction records as JSON, CSV, Excel, XML, or HTML.
Use cases
- Sales research — see which public posts a prospect or buyer reacts to before outreach.
- Account intelligence — track themes and authors receiving engagement from selected profiles.
- Creator and influencer research — analyze the content and people that attract reactions from industry voices.
- Content research — compare reacted-post topics, formats, authors, and engagement levels.
- Automation — send new reaction records to a CRM, warehouse, spreadsheet, webhook, or AI workflow.
Pricing
$2 per 1,000 reaction records ($0.002 per record). You are billed per unique reacted-to-post record saved to the dataset — not per profile or per page.
Integrations
- API — start runs and fetch results from Python, JavaScript, or any HTTP client
- Scheduling — run profile research daily, weekly, or on a custom cadence
- Webhooks — trigger another system when a run succeeds or fails
- Make and Zapier — route records into CRMs, spreadsheets, alerts, or enrichment workflows
- Google Sheets and Excel — export flat columns with nested context retained as JSON cells
- MCP — expose the actor as a structured tool to compatible AI agents
Other LinkedIn Actors by data-slayer
| Actor | What it does |
|---|---|
| LinkedIn Profile Scraper | Full profile data from any LinkedIn profile URL |
| LinkedIn Profile Posts Scraper | Recent posts from a profile, with engagement metrics |
| LinkedIn Company Scraper | Full company profile data |
| LinkedIn Company Posts Scraper | Recent posts from any company page |
| LinkedIn Post Performance Scraper | Likes, comments, shares and reaction breakdown for any post |
| LinkedIn Post Engagers Scraper | Everyone who engaged with a post — commenters, reactors, reposters |
| LinkedIn Post Comments Scraper | Every comment on a post, with commenter profiles |
| LinkedIn Post Reactions Scraper | Everyone who reacted to a post, with reactor profiles |
| LinkedIn Post Reposts Scraper | Everyone who reposted or shared a post |
| LinkedIn Profile Engagers Scraper | Everyone who engaged across a profile's recent posts, ranked by engagement |
| LinkedIn Profile Comments Scraper | Comments a profile left on other people's posts |
| LinkedIn People Search (ICP) | Find people by title, seniority, function, company, location |
| LinkedIn Company Search (ICP) | Find companies by industry, size, location and tech stack |
| LinkedIn Company Employees | Employees at a company, filtered by title, seniority and function |
| LinkedIn Job Scraper | Full details for LinkedIn job postings |
| LinkedIn Job Change Tracker | People who recently changed jobs |
Which LinkedIn actor should I use?
| I have… | And I want… | Use |
|---|---|---|
| A profile URL | Reactions they left on others' posts | LinkedIn Profile Reactions Scraper |
| A profile URL | Comments they left on others' posts | LinkedIn Profile Comments Scraper |
| Profile URL(s) | Their recent posts & engagement | LinkedIn Profile Posts Scraper |
| Profile URL(s) | Full profile data | LinkedIn Profile Scraper |
| A post URL | Everyone who reacted | LinkedIn Post Reactions Scraper |
| A post URL | Likes, comments, shares & reaction breakdown | LinkedIn Post Performance Scraper |
| A post URL | Everyone who engaged (commenters + reactors + reposters) | LinkedIn Post Engagers Scraper |
Example tasks
Ready-made configurations you can run as-is, each with its own guide:
- Build a warm lead list from any LinkedIn post
- Find everyone who commented on a competitor's launch post
- Get the reactors on an industry report post
- Capture the reposters who amplified a post
- Source prospects from a webinar promo post
- Find engagers on a hiring announcement post
- Build an audience from a competitor's whole feed
- Find everyone who engaged with a thought leader this month
- Turn a creator's content into a lead list
- Rank the warmest engagers across a profile's posts
FAQ
Do I need LinkedIn cookies or a LinkedIn login?
No. The input contains public LinkedIn profile URLs; you do not provide LinkedIn session cookies or account credentials.
Does this return the people who reacted to a profile's posts?
No. This actor starts from a person's profile and returns the posts that profile reacted to. The LinkedIn Post Reactions Scraper answers the different question of who reacted to one specific post.
Does reaction_breakdown show the profile's own reaction type?
No. It is the aggregate breakdown for the reacted-to post. Use reaction_action for the public action label supplied for the queried profile.
Can I filter by when the reaction happened?
No reaction timestamp is available. posted_within filters on when the reacted-to post was published, not when the profile reacted to it.
Why can engagement counts differ between runs?
Comments, shares, and reactions keep changing after publication. Each record captures the values reported when that profile operation was fetched.
Why are some values null?
Public records do not always expose every identifier, author value, timestamp, or media field. Null means the value was unavailable or could not be parsed safely; the actor does not fill gaps with guesses.
Can profile-image or attachment links expire?
Yes. LinkedIn-hosted media URLs can be temporary. Store or download permitted assets promptly if your workflow needs them later.
How are large batches handled?
Up to five profiles are processed concurrently in bounded windows. Results are still pushed in normalized input order, and pages for one profile are processed serially.
Limits and data notes
- Pagination is automatic;
max_reactions_per_profileis applied after the post-age filter and duplicate removal. posted_withinuses the reacted-to post's UTC publication timestamp and includes the exact cutoff; posts with missing timestamps are excluded from bounded windows and retained when set toany.post_created_atis the post's publication time, not the time the profile reacted. The actor does not invent an unavailable reaction timestamp.- Post engagement values are a snapshot; if the reported total exceeds the sum of the named reaction columns, the gap appears in
other_reaction_count. - Run status and per-profile counts are written to
RUN_SUMMARYin the key-value store (statuses:succeeded,no_results,partial,failed,capped). Errors are never mixed into the dataset. - Use the actor only for legitimate purposes and handle personal data in compliance with applicable laws and platform terms. This independent actor is not affiliated with or endorsed by LinkedIn.
Feedback and support
If a public profile produces an unexpected result, open an issue from the Actor's Issues tab in Apify Console and include the run ID, sanitized input, and observed behavior. Do not post credentials or private data.
Related actors
More from the same portfolio. Apify only auto-recommends actors in the same category, so here are the rest of ours: