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 resource with the Get Conversations operation, it retrieves a list of LinkedIn conversations associated with the authenticated account. This is useful for scenarios where users want to programmatically access their LinkedIn chat conversations, filter them by creation time, or limit the number of conversations retrieved.

Practical examples include:

  • Fetching recent LinkedIn conversations created after a specific timestamp to monitor new interactions.
  • Retrieving a limited number of conversations for display or further processing in workflows.
  • Filtering conversations related to a specific company where the user has admin rights.

Properties

Name Meaning
Company URN Optional. The unique identifier of a company where the account is an admin (e.g., company:1441). Used to scope conversations to that company.
Connected After Optional. A timestamp filter to only return conversations created after this time.
Count Maximum number of conversations to return. Defaults to 20.
Timeout Timeout duration in seconds for the API request. Defaults to 300 seconds.

Output

The output is an array of JSON objects, each representing a LinkedIn conversation. Each item contains the conversation details as returned by the Horizon Data Wave API. The exact structure depends on the API response but typically includes conversation metadata such as participants, last message, timestamps, and conversation IDs.

No binary data output 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 make HTTP POST requests.
  • 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 is configured and selected in the node.
  • Account ID is missing in credentials!: Verify that the credentials include a valid account ID.
  • Timeouts or slow responses: Adjust the "Timeout" property to allow more time for the API to respond.
  • Empty results: Check if the "Connected After" timestamp filter is too restrictive or if the "Count" is set too low.
  • API errors: If the API returns errors, verify that the company URN (if used) is correct and that the account has admin rights for that company.

Links and References

Discussion