Actions7
Overview
The "Scrape Profiles From A LinkedIn Search" operation in this custom n8n node automates the process of extracting profile data from LinkedIn search results. It allows users to either specify search filters (such as category, search term, city, and country) or provide a direct LinkedIn search URL. The node can scrape multiple pages of results, making it useful for lead generation, recruitment, market research, or any scenario where bulk LinkedIn profile data is needed.
Practical examples:
- Recruiters gathering lists of potential candidates based on specific skills and locations.
- Sales teams building prospect lists filtered by industry, company size, or geography.
- Researchers collecting company or person profiles for analysis.
Properties
| Name | Type | Meaning |
|---|---|---|
| Search Method | options | Choose how to perform the LinkedIn search: "Use Filters" lets you set parameters like category, search term, city, and country; "Use Search URL" lets you paste a full LinkedIn search URL with your desired filters already applied. |
| Category | options | Select whether to scrape "Persons" or "Companies". Only available when using the "Use Filters" search method. |
| Search URL | string | The full LinkedIn search URL to scrape from. Only used if "Search Method" is set to "Use Search URL". |
| Search Term | string | The keyword(s) to use for searching profiles. Required when using the "Use Filters" search method. |
| City | string | Filter search results by city. Only available when using the "Use Filters" search method. |
| Country | string | Filter search results by country. Only available when using the "Use Filters" search method. |
| Start Page | number | The starting page number for scraping (useful for pagination). Default is 1. |
| Number of Pages | number | The number of result pages to scrape. Default is 1. |
Output
The node returns a JSON array containing the scraped LinkedIn profiles. Each item typically represents a single profile (person or company), including details such as name, headline, location, and profile URL. The exact structure may vary depending on LinkedIn's current layout and the scraping implementation, but generally includes:
[
{
"name": "John Doe",
"headline": "Software Engineer at Example Corp",
"location": "San Francisco Bay Area",
"profileUrl": "https://www.linkedin.com/in/johndoe/",
// ...other available fields
},
...
]
- If companies are selected, the output will contain company-related fields.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Browserflow API (https://app.browserflow.io/api/).
- API Key: You must configure valid
browserflowApicredentials in n8n. - LinkedIn Account: The underlying automation relies on access to LinkedIn via Browserflow.
Troubleshooting
Common Issues:
- Invalid or expired Browserflow API key: Ensure your API credentials are correct and active.
- LinkedIn search URL not working: Make sure the URL is copied directly from LinkedIn after applying your desired filters.
- Empty or incomplete results: LinkedIn may limit visible profiles due to privacy settings, account restrictions, or anti-scraping measures.
- Rate limits or CAPTCHAs: Excessive scraping may trigger LinkedIn's anti-bot protections.
Error Messages & Resolutions:
- "401 Unauthorized" or similar: Check your Browserflow API credentials.
- "400 Bad Request": Verify that all required fields (e.g., Search Term when using filters) are filled and that the Search URL is valid.
- "No results found": Adjust your filters or try a different search term/category.