Actions9
Overview
This node automates scraping LinkedIn profiles based on search criteria using the Browserflow API. It supports two main methods for searching:
- Using Filters: You specify search parameters such as category (persons or companies), search term, city, and country to filter LinkedIn search results.
- Using Search URL: You provide a full LinkedIn search URL directly to scrape profiles from that specific search.
The node can paginate through multiple pages of search results by specifying the start page and number of pages to scrape.
Common scenarios:
- Gathering leads or contacts by scraping LinkedIn profiles matching certain keywords and locations.
- Market research by collecting company profiles from LinkedIn searches.
- Automating data collection workflows where LinkedIn profile data is needed without manual browsing.
Practical example:
You want to collect profiles of marketing managers in New York City. You set the search method to "Use Filters," choose "Persons" as the category, enter "Marketing Manager" as the search term, specify "New York" as the city, and set the number of pages to 3. The node scrapes profiles matching these filters across three pages.
Alternatively, if you have a complex LinkedIn search URL with multiple filters applied, you can use the "Use Search URL" method and provide that URL directly to scrape profiles accordingly.
Properties
| Name | Meaning |
|---|---|
| Search Method | Choose how to perform the LinkedIn search: - Use Filters - Use Search URL |
| Category | The category to scrape: - Persons - Companies Only shown when using filters method |
| Search URL | The full LinkedIn search URL to scrape from. Only shown when using search URL method |
| Search Term | The search term to use for scraping profiles (e.g., job title, keyword). Required when using filters. |
| City | Filter search results by city. Optional, used only with filters method. |
| Country | Filter search results by country. Optional, used only with filters method. |
| Start Page | The starting page number to begin scraping from. Useful for pagination. |
| Number of Pages | How many pages of search results to scrape. |
Output
The node outputs an array of JSON objects representing the scraped LinkedIn profiles. Each object contains profile data returned by the Browserflow API, which typically includes details such as:
- Profile name
- Headline or job title
- Location
- Company information (if applicable)
- Other publicly available LinkedIn profile fields depending on the search category
No binary data output is produced by this operation.
Dependencies
- Requires an active Browserflow API key credential configured in n8n to authenticate requests.
- Relies on the external Browserflow API endpoint at
https://app.browserflow.io/api/to perform LinkedIn scraping. - Internet access is required for the node to communicate with the Browserflow service.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an incorrect or malformed LinkedIn search URL may result in no data or errors.
- Exceeding rate limits or usage quotas imposed by the Browserflow API could lead to request failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors include HTTP status codes and descriptive messages from the Browserflow API.
- Example: "An error with status 401 occurred" indicates unauthorized access due to invalid API key.
- "Unknown error" may indicate unexpected issues; check network and API availability.
Resolution tips:
- Verify the API key is correctly set up in n8n credentials.
- Double-check the LinkedIn search URL or filter parameters for correctness.
- Monitor API usage and respect any rate limits.
- Ensure stable internet connection.