HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API

Actions8

Overview

This node, named "HDW LinkedIn Management," allows users to manage LinkedIn accounts through the Horizon Data Wave API. Specifically for the User resource with the Get Connections operation, it retrieves a list of LinkedIn connections for a specified user. Users can filter connections based on when they were connected (using a timestamp) and limit the number of returned connections.

Common scenarios include:

  • Fetching recent LinkedIn connections added after a certain date.
  • Retrieving a limited set of connections for analysis or integration with other systems.
  • Automating LinkedIn network management by periodically syncing connection data.

Example use case: A recruiter wants to get all new connections made by a LinkedIn user since last week to analyze potential candidates.

Properties

Name Meaning
Connected After Filter users that were connected after this timestamp (Unix timestamp in seconds).
Count Maximum number of connections to return (default is 20).
Timeout Timeout in seconds for the API request (default is 300 seconds).

Output

The output is an array of JSON objects representing LinkedIn user connections. Each item corresponds to one connection retrieved from the API. The exact structure depends on the API response but typically includes details about each connected user.

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 send requests.
  • Proper configuration of the API credentials within n8n is necessary.
  • The node sends POST requests to /api/linkedin/management/user/connections endpoint with parameters including account ID, optional connectedAfter timestamp, and count.

Troubleshooting

  • No credentials provided!: This error occurs if the required API authentication token is missing. Ensure the API key credential is configured correctly in n8n.
  • Account ID is missing in credentials!: The API requires an account ID linked to the credentials. Verify that the credential setup includes this information.
  • Timeouts or slow responses: Adjust the "Timeout" property to allow more time for the API to respond, especially when requesting many connections.
  • Empty results: If no connections are returned, check the "Connected After" filter value and ensure the user has connections matching the criteria.

Links and References

Discussion