Scrape LinkedIn Search Post Engagers to Google Sheets
Search LinkedIn for posts by keyword, then extract everyone who reacted to each post. Paste a fetch() for a Content search from DevTools to scrape all engagers with automatic pagination.
Last updated
February 18, 2026
Connectors used
Tags
Key Takeaways
- Keyword-based search - Search LinkedIn posts by any keyword and scrape everyone who reacted
- Automatic pagination - Pages through search results and reaction lists with 3-second delays
- Rich profile data - Extracts name, headline, LinkedIn URL, profile ID, and the post they engaged with
- Up to 1,000 profiles - Collects up to 100 reactors per post across multiple search pages
- Real-time export - Saves profiles to Google Sheets as each post is processed
- DevTools-based - You paste a fetch() request copied from a LinkedIn Content search
What This Workflow Does
This workflow takes a LinkedIn Content search API request (copied from DevTools), paginates through search results to find posts matching your keyword, then fetches the reactor list for each post. It extracts full profile details (name, headline, LinkedIn URL, profile ID) and saves everything to Google Sheets.
Use cases:
- Find people engaging with content about a specific topic (e.g., "AI agency", "n8n consultants")
- Build targeted outreach lists based on content engagement
- Discover professionals actively interested in a niche by their reactions
- Research which audiences engage with posts about specific keywords
How It Works
| Step | What Happens |
|---|---|
| 1. Manual trigger | You paste a fetch() request from a LinkedIn Content search |
| 2. Parse fetch request | Code node extracts the base URL, headers, CSRF token, and search keywords |
| 3. Search for posts | HTTP request fetches a page of search results matching your keyword |
| 4. Extract post activity IDs | Code node pulls activity IDs from the search result clusters |
| 5. Fetch reactions per post | For each post, HTTP request fetches up to 100 reactors with a 3-second delay |
| 6. Extract reactor profiles | Code node collects name, headline, LinkedIn URL, and profile ID from each reactor |
| 7. Save to Google Sheets | AI agent writes profiles to your spreadsheet |
The workflow alternates between searching for new posts and scraping reactors, stopping after ~1,000 profiles or when all posts and search pages are exhausted.
AI Models Used
| Model | Provider | Role |
|---|---|---|
| Gemini 3 Flash (Preview) | Writes reactor profiles to Google Sheets |
Setup Instructions
- Click "Use template" on this page
- Copy the template Google Sheet linked inside the workflow and paste your own sheet URL into the AI node
- Connect your Google Sheets account
- Go to LinkedIn and search for your topic (e.g., "AI agency")
- Click the Posts tab to filter by content
- Open DevTools (F12), go to the Network tab, and filter by "graphql" or "voyager"
- Scroll or navigate in the search results to trigger the API call
- Find the
searchDashClustersrequest, right-click it, and select "Copy as fetch" - Paste the fetch() into the Manual Trigger node
- Run the workflow
Google Sheets Output
| Column | Field |
|---|---|
| A | name |
| B | linkedin_url |
| C | headline |
| D | profile_id |
| E | post_url |
| F | search_query |
Customization
| What You Can Change | How |
|---|---|
| Search keyword | Copy a fetch() from a different LinkedIn Content search |
| Delay between requests | Edit the wait node duration (default is 3 seconds) |
| Max profiles | Change the MAX_PROFILES constant in the process code node (default is 1,000) |
| Output columns | Modify the AI node prompt to write additional or fewer columns |
| Target Google Sheet | Replace the sheet URL in the AI node prompt |
FAQ
Q: Does this require LinkedIn Premium? A: No, it works with a free LinkedIn account. You just need to be logged in.
Q: How many profiles can I extract per run? A: Up to 1,000 profiles. Each post yields up to 100 reactors, and the workflow paginates through search results to find more posts.
Q: What is the difference between this and the Viral Post Leads workflow? A: The Viral Post Leads workflow targets a single post you already know about. This workflow searches LinkedIn by keyword to discover posts and then scrapes the engagers from all of them automatically.
Q: Why do I need to click the Posts tab? A: The Posts tab activates the Content search endpoint. The workflow needs this specific API request to paginate through post results.
Q: What if my search returns fewer results than expected? A: LinkedIn limits Content search results. The workflow processes whatever is available and stops when there are no more pages or posts to scrape.
Q: Can I run this for multiple keywords? A: Run the workflow once per keyword. Each run uses a single search query.
Want to showcase your own workflows?
Become a Needle workflow partner and turn your expertise into recurring revenue.
