HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API

Overview

This node enables managing LinkedIn posts and comments through the Horizon Data Wave API. Specifically, for the Post resource with the Create Comment operation, it allows users to create a comment on an existing LinkedIn post or comment by specifying the text content and the target post/comment URN.

Common scenarios include:

  • Adding comments to LinkedIn posts programmatically as part of social media automation.
  • Responding to discussions on LinkedIn posts or nested comments in bulk workflows.
  • Integrating LinkedIn engagement into broader marketing or CRM automation pipelines.

Example: Automatically posting a comment like "Thanks for sharing this insight!" on a specific LinkedIn post identified by its URN.

Properties

Name Meaning
Text The content of the comment to be created on the LinkedIn post or comment.
Post/Comment URN The unique identifier (URN) of the LinkedIn activity or comment to which this new comment will be added. Examples: "activity:123" or "comment:(activity:123,456)".
Timeout Maximum time in seconds to wait for the API response before timing out. Defaults to 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 URN, text content, timestamps, and possibly metadata related to the comment's status.

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

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Horizon Data Wave LinkedIn Management API.
  • The node makes authenticated HTTP POST requests to https://api.horizondatawave.ai/api/linkedin/management/post/comment.
  • Proper configuration of the API credentials within n8n is necessary.
  • Network connectivity to the Horizon Data Wave API endpoint is required.

Troubleshooting

  • Missing Credentials Error: If no API credentials are provided, the node throws an error. Ensure that the API key credential is configured correctly in n8n.
  • Account ID Missing: The node expects an account ID within the credentials; if missing, it will error out. Verify that the credential setup includes the required account identification.
  • Timeouts: If the API does not respond within the specified timeout, the request may fail. Adjust the "Timeout" property as needed.
  • API Errors: The node surfaces detailed API error messages including HTTP status, error headers, request IDs, and execution times when available. Common issues might include invalid URNs, insufficient permissions, or rate limiting.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.

Links and References

Discussion