Actions9
Overview
This node integrates with the Browserflow API to automate various LinkedIn actions. Specifically, for the "Send A LinkedIn Message" operation, it allows users to send a direct message to a specified LinkedIn profile URL programmatically. This is useful in scenarios such as automating outreach campaigns, following up with contacts, or sending personalized messages at scale without manual intervention.
Practical examples include:
- Sending welcome messages to new connections.
- Automating follow-ups after networking events.
- Delivering targeted marketing messages to prospects identified by their LinkedIn profiles.
Properties
| Name | Meaning |
|---|---|
| LinkedIn URL | The LinkedIn profile URL of the recipient to whom the message will be sent. |
| Message | The content of the message to send. Must comply with LinkedIn's character and message limits. |
Output
The node outputs a JSON array where each element corresponds to the response from the Browserflow API for each input item processed. For the "Send A LinkedIn Message" operation, the output JSON typically contains the result of the message sending request, which may include success status, any error messages, or metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active API key credential for the Browserflow service to authenticate requests.
- The node makes HTTP POST requests to the Browserflow API endpoint at
https://app.browserflow.io/api/linkedin-send-message. - Proper configuration of the Browserflow API credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or expired API key leading to authentication errors.
- Incorrect or malformed LinkedIn profile URLs causing the API to reject the request.
- Messages exceeding LinkedIn's allowed character limits resulting in failure.
- Network connectivity issues preventing communication with the Browserflow API.
Error Messages:
- Errors include HTTP status codes and descriptive messages returned by the API.
- The node throws errors with messages like "An error with status [code] occurred" along with details extracted from the API response.
Resolutions:
- Verify that the API key credential is correctly set and has not expired.
- Ensure the LinkedIn URL is valid and publicly accessible.
- Keep message length within LinkedIn's limits.
- Check network connectivity and proxy settings if applicable.
Links and References
- Browserflow Official Website
- LinkedIn Messaging Guidelines
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)