Actions8
- User Actions
- Chat Actions
- Post Actions
Overview
This node enables managing LinkedIn accounts via the Horizon Data Wave API. It supports operations related to LinkedIn users, chats, and posts, allowing automation of common LinkedIn management tasks such as sending connection invitations, retrieving connections, sending and fetching chat messages, creating posts, and commenting on posts.
Typical use cases include:
- Automating outreach by sending connection requests to LinkedIn users.
- Extracting user connections or conversations for CRM or analytics purposes.
- Managing LinkedIn content by programmatically creating posts or comments.
- Handling LinkedIn messaging workflows by sending and retrieving chat messages.
For example, a marketing team could automate sending personalized connection requests and follow-up messages, or a social media manager could schedule and publish LinkedIn posts automatically.
Properties
| Name | Meaning |
|---|---|
| Timeout | Timeout in seconds for each API request (default is 300 seconds). |
Note: The node also supports other input properties depending on the selected Resource and Operation, but since only the "Timeout" property was provided, it is listed here.
Output
The node outputs an array of JSON objects representing the response data from the Horizon Data Wave API for each input item processed. The structure of each JSON object depends on the specific operation performed:
- For user-related operations, it may return connection details, profile information, or confirmation of sent connection invitations.
- For chat-related operations, it returns message or conversation data.
- For post-related operations, it returns details about created posts or comments.
If multiple items are returned by the API, each is output as a separate JSON object in the array.
The node does not output binary data.
Dependencies
- Requires an API key credential for the Horizon Data Wave LinkedIn API.
- The node makes HTTP POST requests to
https://api.horizondatawave.aiendpoints. - Proper configuration of the API credentials with account ID is necessary.
- Network access to the Horizon Data Wave API endpoint must be available.
Troubleshooting
No credentials provided!
This error occurs if the required API authentication token is missing. Ensure that valid credentials are configured in n8n before running the node.Account ID is missing in credentials!
The API requires an account identifier within the credentials. Verify that the account ID is correctly set in the credential configuration.Timeouts or slow responses
Adjust the "Timeout" property to allow more time for API responses if network latency or large data volumes cause delays.API errors or unexpected responses
Check the Horizon Data Wave API documentation and ensure that all required parameters for the chosen resource and operation are correctly provided.
Links and References
- Horizon Data Wave API Documentation (hypothetical link based on API base URL)
- LinkedIn Developer Documentation (for understanding LinkedIn URNs and concepts)
