Actions9
Overview
This node automates sending LinkedIn connection invites using the Browserflow API. It is designed to streamline and automate the process of connecting with professionals on LinkedIn by programmatically sending connection requests, optionally including a personalized message.
Common scenarios where this node is beneficial:
- Automating outreach campaigns for networking or sales prospecting.
- Quickly building a professional network by sending multiple connection invites.
- Personalizing connection requests with custom messages to increase acceptance rates.
Practical example:
You want to send a connection invite to a list of LinkedIn profiles collected from a lead generation workflow. Using this node, you provide each profile's LinkedIn URL and optionally add a custom message tailored to each contact, automating the entire invitation process without manual intervention.
Properties
| Name | Meaning |
|---|---|
| LinkedIn URL | The LinkedIn profile URL to which the connection invite will be sent. This is required. |
| Add Message | Boolean flag indicating whether to include a custom message in the connection invite. |
| Message | Optional text message to include in the connection invite. If left blank, the invite is sent without a message to avoid LinkedIn limits. Must fit within LinkedIn's character and message restrictions. Only shown if "Add Message" is true. |
Output
The node outputs a JSON array where each element corresponds to the result of sending a connection invite for an input item.
- The JSON output contains the response returned by the Browserflow API after attempting to send the invite.
- The structure typically includes success status and any relevant metadata or error information from the API.
- No binary data is output by this node.
Dependencies
- Requires an active API key credential for the Browserflow service, configured in n8n.
- The node makes HTTP POST requests to the Browserflow API endpoint
https://app.browserflow.io/api/linkedin-connection-invite. - Proper internet connectivity and valid API credentials are necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing LinkedIn URL: Ensure the LinkedIn profile URL is correctly formatted and accessible.
- API authentication errors: Verify that the API key credential is correctly set up and has not expired or been revoked.
- LinkedIn rate limits or restrictions: Sending too many invites or including messages may trigger LinkedIn limits; consider sending invites without messages or spacing out requests.
- Message length violations: Custom messages must comply with LinkedIn's character limits; overly long messages may cause errors.
Common error messages:
"An error with status XXX occurred": Indicates an HTTP error status returned by the API. Check the status code and message for details.- Errors mentioning invalid credentials or authorization failures suggest checking the API key setup.
- Network-related errors imply connectivity issues or incorrect API endpoint configuration.
To resolve errors, verify input parameters, ensure valid credentials, and consult LinkedIn's usage policies regarding connection invites.
Links and References
- Browserflow API Documentation (for detailed API endpoints and usage)
- LinkedIn Help - Inviting Connections (LinkedIn official guidelines on connection invites)
- n8n Documentation - HTTP Request Node (for understanding HTTP request handling in n8n)