HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API
Join our community

Actions8

Overview

The node integrates with the Horizon Data Wave API to manage LinkedIn chat conversations. Specifically, the Get Conversations operation retrieves a list of LinkedIn chat conversations associated with a company account where the user has admin rights.

This operation is useful for scenarios such as:

  • Monitoring recent LinkedIn conversations within a company.
  • Extracting conversation metadata for analytics or reporting.
  • Automating workflows based on new or updated conversations.

For example, a user could fetch all conversations created after a certain timestamp to process only recent chats or limit the number of conversations retrieved to avoid excessive data.

Properties

Name Meaning
Company URN The unique identifier of the company where the account has admin rights (e.g., company:1441). Must include prefix.
Connected After Optional filter to return only conversations created after this Unix timestamp (in seconds).
Count Maximum number of conversations to return. Defaults to 20.
Timeout Request timeout in seconds. Defaults to 300 seconds.

Output

The output is an array of JSON objects, each representing a LinkedIn conversation. The exact structure depends on the API response but typically includes conversation metadata such as participants, timestamps, and message summaries.

If multiple conversations are returned, each is output as a separate item in the node's output array.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the Horizon Data Wave LinkedIn Management API.
  • The credential must include an account ID used to identify the LinkedIn account.
  • The node makes HTTP POST requests to the Horizon Data Wave API endpoint at https://api.horizondatawave.ai/api/linkedin/management/conversations.
  • Proper network access to the API endpoint is required.

Troubleshooting

  • No credentials provided!
    This error occurs if the node is executed without valid API credentials configured. Ensure that the API key credential is set up correctly in n8n.

  • Account ID is missing in credentials!
    The API credential must contain an account ID identifying the LinkedIn account. Verify that the credential configuration includes this information.

  • API errors with HTTP status codes
    The node surfaces detailed API error messages including HTTP status, request ID, execution time, and token usage points when available. Common issues may include invalid company URN, insufficient permissions, or rate limiting.

  • Timeouts
    If the request times out, consider increasing the "Timeout" property value.

  • Empty results
    If no conversations are returned, verify the "Company URN" and "Connected After" filters to ensure they match existing conversations.

Links and References

Discussion