HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API
Join our community

Actions8

Overview

This node integrates with the Horizon Data Wave API to manage LinkedIn accounts, specifically focusing on chat-related operations in this context. The Get Messages operation under the Chat resource retrieves chat messages exchanged with a specified LinkedIn user.

Typical use cases include:

  • Fetching conversation history with a LinkedIn contact for CRM or customer support purposes.
  • Archiving or analyzing message exchanges for insights or compliance.
  • Automating workflows that depend on recent chat interactions.

For example, a user might want to pull all messages from a particular LinkedIn user to review communication before a sales call or to trigger follow-up actions based on message content.

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 The maximum time in seconds to wait for the API response before timing out. Default is 300 seconds.

Output

The output is an array of JSON objects representing individual chat messages retrieved from the LinkedIn conversation with the specified user. Each item contains the message details as returned by the Horizon Data Wave API.

No binary data is produced by this operation.

Example output structure (simplified):

[
  {
    "json": {
      "messageId": "string",
      "sender": "string",
      "recipient": "string",
      "text": "string",
      "timestamp": "ISO8601 datetime string",
      ...
    }
  },
  ...
]

Dependencies

  • Requires an active connection to the Horizon Data Wave API via an API key credential.
  • The node expects valid credentials containing an account ID.
  • Network access to https://api.horizondatawave.ai must be available.
  • Proper permissions on the LinkedIn account and company (if specified) are necessary to fetch chat messages.

Troubleshooting

  • No credentials provided!
    Ensure that the node is configured with valid API authentication credentials.

  • Account ID is missing in credentials!
    Verify that the credentials include a valid account identifier required by the API.

  • Timeouts or slow responses
    Increase the Timeout property value if the API takes longer to respond, especially when retrieving large message histories.

  • API errors with HTTP status codes
    The node surfaces detailed error information including HTTP status, API error messages, request IDs, and execution times. Use these details to diagnose issues such as permission problems, invalid URNs, or rate limiting.

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

Links and References

Discussion