Actions9
Overview
This node integrates with the Browserflow API to automate various LinkedIn-related tasks. Specifically, for the List LinkedIn Connections operation, it retrieves a list of your LinkedIn connections with options to limit the number of results, skip a certain number of connections (offset), and apply sorting filters.
Typical use cases include:
- Exporting your LinkedIn connections for CRM or marketing purposes.
- Analyzing your network by fetching connection data in bulk.
- Automating outreach workflows by retrieving connection lists programmatically.
For example, you could set the node to fetch the first 100 connections sorted by recently added, then use that data downstream to send personalized messages or invitations.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of connection results to return. Minimum value is 1. |
| Offset | Number of connections to skip before starting to retrieve results. Useful for pagination. |
| Filter | Sort filter applied to the connections list. Options: "Recently Added", "First Name", "Last Name". |
Output
The node outputs an array of JSON objects representing LinkedIn connections. Each object contains details about a single connection as returned by the Browserflow API. The exact structure depends on the API response but typically includes fields such as name, profile URL, headline, and other LinkedIn profile metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active API key credential for the Browserflow service.
- The node makes HTTP POST requests to the Browserflow API endpoint at
https://app.browserflow.io/api/linkedin-list-connections. - Proper internet connectivity and valid authentication are necessary.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Exceeding rate limits or quota restrictions imposed by Browserflow API may result in errors.
- Providing invalid parameter values (e.g., negative limit or offset) might cause request rejections.
Error messages:
- Errors include HTTP status codes and descriptive messages from the API.
- Typical error message format: "An error with status [code] occurred" along with detailed description.
- To resolve, verify API credentials, check parameter values, and ensure the API service is operational.
Links and References
- Browserflow Official Website
- LinkedIn API Documentation
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)