Actions9
Overview
This node, named "Browserflow for LinkedIn," automates various LinkedIn-related tasks by interacting with the Browserflow API. Specifically, the "Scrape LinkedIn Posts" operation allows users to scrape posts from a specified LinkedIn profile URL, which can be either a personal or company profile. This is useful for gathering content data such as post text, timestamps, and engagement metrics for analysis, marketing research, or competitive intelligence.
Practical examples include:
- Collecting recent posts from a competitor’s LinkedIn page to analyze their content strategy.
- Aggregating posts from a company’s LinkedIn profile for sentiment analysis or reporting.
- Monitoring updates and announcements posted on a personal LinkedIn profile.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of posts to return. Must be at least 1. Defaults to 50. |
| Offset | Number of posts to skip before starting to scrape. Useful for pagination. Defaults to 0. |
| LinkedIn URL | The LinkedIn profile URL to scrape posts from. Supports both person and company profiles. |
Output
The output is a JSON array where each element represents the scraped data returned by the Browserflow API for the requested LinkedIn posts. The exact structure depends on the API response but typically includes details about each post such as content, author, timestamp, and engagement statistics.
No binary data output is indicated by the code.
Dependencies
- Requires an API key credential for the Browserflow service to authenticate requests.
- The node makes HTTP POST requests to the Browserflow API endpoint
https://app.browserflow.io/api/linkedin-scrape-posts. - Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing LinkedIn profile URL will cause the API to fail.
- Exceeding rate limits or quota restrictions on the Browserflow API may result in errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors include HTTP status codes and descriptive messages extracted from the API response.
- Example error message format: "An error with status [code] occurred" with additional description.
Resolution tips:
- Verify the LinkedIn URL is correct and publicly accessible.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and retry if transient errors occur.
- Review API usage limits and adjust request frequency accordingly.
Links and References
- Browserflow API Documentation (for detailed API endpoints and parameters)
- LinkedIn Help Center (for understanding LinkedIn profile URLs and privacy settings)