HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API

Actions8

Overview

The node "HDW LinkedIn Management" enables managing LinkedIn accounts through the Horizon Data Wave API. Specifically, for the Chat - Get Messages operation, it retrieves chat messages exchanged with a specified LinkedIn user. This is useful for workflows that need to analyze or archive LinkedIn conversations, automate responses, or integrate LinkedIn messaging data into CRM or customer support systems.

Practical examples:

  • Automatically fetching recent chat messages with a LinkedIn contact to trigger follow-up actions.
  • Archiving LinkedIn message history for compliance or record-keeping.
  • Integrating LinkedIn chat data into a helpdesk or sales platform.

Properties

Name Meaning
User URN The unique identifier of the LinkedIn user whose chat messages you want to retrieve. Must include prefix (e.g., fsd_profile:ACoAA...).
Company URN (Optional) The company identifier where the account has admin rights. Must include prefix (e.g., company:1441). Used to specify context if applicable.
Timeout Timeout duration in seconds for the API request. Default is 300 seconds.

Output

The output is an array of JSON objects representing the chat messages retrieved from the LinkedIn conversation with the specified user. Each item corresponds to a single message or message metadata as returned by the Horizon Data Wave API.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • No credentials provided!: Ensure that the API key credential for Horizon Data Wave LinkedIn API is configured and selected in the node.
  • Account ID is missing in credentials!: Verify that the credentials include a valid account ID required for API calls.
  • Timeouts or slow responses: Adjust the "Timeout" property to allow more time for the API response if network latency or large data volumes are expected.
  • Invalid User URN format: Make sure the User URN includes the correct prefix (e.g., fsd_profile:) as required by the API.
  • Empty or no messages returned: Confirm that there are existing messages with the specified user and that the user URN is correct.

Links and References

Discussion