HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API
Join our community

Actions8

Overview

The node "HDW LinkedIn Management" enables interaction with LinkedIn accounts via the Horizon Data Wave API. Specifically, for the Chat - Send Message operation, it allows sending chat messages to LinkedIn users by specifying their User URN and optionally a Company URN where the account has admin rights.

This node is useful in scenarios such as automating outreach, customer engagement, or internal communications on LinkedIn without manual intervention. For example, a sales team could automatically send personalized messages to leads, or HR could notify candidates through LinkedIn chat.

Properties

Name Meaning
User URN The unique identifier of the LinkedIn user to whom the message will be sent. Must include prefix (e.g., fsd_profile:ACoAA...).
Company URN (Optional) The company identifier where the authenticated account has admin rights. Must include prefix (e.g., company:1441). Used to specify context if needed.
Message Text The actual text content of the chat message to send.
Timeout Maximum time in seconds to wait for the API response before timing out. Default is 300 seconds.

Output

  • The output JSON contains the response from the Horizon Data Wave API after sending the message.
  • If multiple input items are processed, each result is returned as an individual JSON object in the output array.
  • The structure of the JSON depends on the API response but generally includes details about the sent message or any errors.
  • No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for the Horizon Data Wave LinkedIn API.
  • The node uses the base URL https://api.horizondatawave.ai to send requests.
  • Proper configuration of the API credentials within n8n is necessary.
  • The authenticated account ID must be present in the credentials.

Troubleshooting

  • No credentials provided!
    This error occurs if the API key credential is missing or not configured. Ensure the credential is set up correctly in n8n.

  • Account ID is missing in credentials!
    The API requires an account ID linked to the credentials. Verify that the credential includes a valid account ID.

  • Timeouts or slow responses
    Adjust the "Timeout" property if the API takes longer to respond.

  • API Errors with HTTP status codes
    The node captures detailed API error information including HTTP status, error messages, request IDs, and execution times. Review these details to diagnose issues like invalid URNs, permission problems, or rate limits.

  • Invalid User URN format
    Make sure the User URN includes the required prefix (e.g., fsd_profile:).

  • Company URN usage
    If specifying a Company URN, ensure the authenticated account has admin rights for that company.

Links and References

Discussion