HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API

Actions8

Overview

This node enables managing LinkedIn posts through the Horizon Data Wave API, specifically allowing users to create comments on existing LinkedIn posts or comments. It is useful for automating engagement on LinkedIn by programmatically adding comments to posts or replies to comments, which can help in social media management, marketing campaigns, or customer interaction workflows.

For example, you could use this node to automatically add a comment to a newly created post or respond to comments on your posts as part of an automated workflow.

Properties

Name Meaning
Text The content text of the comment to be created.
Post/Comment URN The unique resource name (URN) identifying the LinkedIn activity (post) or comment to which the new comment will be added. Examples: "activity:123" or "comment:(activity:123,456)".
Timeout The maximum time in seconds to wait for the API request to complete before timing out. Default is 300 seconds.

Output

The node outputs JSON data representing the response from the Horizon Data Wave API after creating the comment. This typically includes details about the newly created comment such as its ID, content, and metadata returned by the API.

If multiple items are processed, the output is an array of such JSON objects, each corresponding to one comment creation operation.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Horizon Data Wave API with valid credentials including an account identifier.
  • The node uses an API key credential configured in n8n to authenticate requests.
  • Network access to https://api.horizondatawave.ai is required.

Troubleshooting

  • No credentials provided!
    This error occurs if the node is executed without setting up the required API authentication credentials. To fix, configure the necessary API key credential in n8n.

  • Account ID is missing in credentials!
    The API credentials must include an account ID. Ensure that the credentials used contain this information.

  • Timeouts or slow responses
    If the API takes longer than the specified timeout (default 300 seconds), the request may fail. Adjust the "Timeout" property as needed.

  • Invalid URN format
    The "Post/Comment URN" must be correctly formatted. Incorrect URNs will cause the API to reject the request. Verify the URN string matches expected patterns like "activity:123" or "comment:(activity:123,456)".

Links and References

Discussion