Actions9
Overview
This node automates the process of scraping LinkedIn profiles from a specific LinkedIn post, including optionally extracting profiles from comments and reactions on that post. It is useful for gathering detailed information about users engaging with a particular LinkedIn post, such as for marketing research, lead generation, or social media analysis.
Typical use cases include:
- Extracting profiles of people who commented on a LinkedIn post to follow up or analyze engagement.
- Collecting profiles of users who reacted to a post to understand audience demographics.
- Combining both comments and reactions data to get a comprehensive list of engaged users.
For example, a marketer could input a LinkedIn post URL and retrieve profiles of commenters and reactors to target them with personalized campaigns.
Properties
| Name | Meaning |
|---|---|
| Post URL | The URL of the LinkedIn post to scrape profiles from. |
| Add Comments | Whether to include profiles from the comments in the scrape results (true/false). |
| Comments Offset | Number of comments to skip before starting to scrape (used if Add Comments is true). |
| Comments Limit | Maximum number of comments to scrape (used if Add Comments is true). |
| Add Reactions | Whether to include profiles from the reactions in the scrape results (true/false). |
| Reactions Offset | Number of reactions to skip before starting to scrape (used if Add Reactions is true). |
| Reactions Limit | Maximum number of reactions to scrape (used if Add Reactions is true). |
Output
The node outputs an array of JSON objects representing the scraped LinkedIn profiles associated with the specified post. The output includes profile details extracted from commenters and/or reactors depending on the selected options.
The exact structure of each profile object depends on the external API response but typically contains user identifiers, names, profile URLs, and possibly additional metadata related to their interaction with the post.
No binary data output is produced by this node.
Dependencies
- Requires an active API key credential for the Browserflow service, which provides the LinkedIn automation backend.
- The node makes HTTP POST requests to the Browserflow API endpoint
https://app.browserflow.io/api/linkedin-scrape-profiles-from-post-comments. - Proper network connectivity and valid API credentials are necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or expired API key will cause authentication failures.
- Incorrect or malformed LinkedIn post URL may result in no data or errors.
- Rate limits or API usage restrictions from the Browserflow service can cause request failures.
- If "Add Comments" or "Add Reactions" is enabled but offset or limit values are incorrect, it might return incomplete or empty results.
Error messages:
- Errors include HTTP status codes and descriptive messages returned from the API.
- Typical error message format: "An error with status [code] occurred" with additional description from the API response.
- To resolve, verify API key validity, check the LinkedIn post URL correctness, and ensure parameters like offsets and limits are within acceptable ranges.
Links and References
- Browserflow for LinkedIn Documentation (general reference for the API used)
- LinkedIn Post URL Format Guidelines (to ensure correct post URL input)