HDW LinkedIn Management icon

HDW LinkedIn Management

Manage LinkedIn accounts through Horizon Data Wave API

Overview

This node, named "HDW LinkedIn Management," enables managing LinkedIn accounts via the Horizon Data Wave API. Specifically for the User resource with the Send Connection operation, it sends a connection invitation to a specified LinkedIn user by their User URN.

Common scenarios include automating LinkedIn outreach campaigns, integrating LinkedIn connection requests into workflows, or bulk sending connection invitations based on external triggers.

For example, you could use this node to automatically send connection requests to new leads imported from a CRM system, helping streamline networking efforts.

Properties

Name Meaning
User URN The unique identifier of the LinkedIn user to whom the connection invitation will be sent. Must include the prefix (e.g., fsd_profile:ACoAA...).
Timeout The maximum time in seconds to wait for the API response before timing out. Default is 300 seconds.

Output

The node outputs JSON data representing the API response from the Horizon Data Wave service after attempting to send the connection request. This typically includes confirmation details or error information related to the connection invitation.

If multiple input items are processed, the output is an array where each element corresponds to the result of one connection request.

No binary data is produced by 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 for authentication.
  • Network access to the Horizon Data Wave API must be available.

Troubleshooting

  • No credentials provided!
    This error occurs if the API key credential is missing. Ensure that valid credentials are configured in n8n.

  • Account ID is missing in credentials!
    The API requires an account ID associated with the credentials. Verify that the credential setup includes this information.

  • Timeouts or slow responses
    If the API call takes longer than the specified timeout, increase the "Timeout" property value.

  • API errors with HTTP status codes
    The node captures detailed API error messages and headers when available. Common issues might include invalid User URN format, rate limiting, or permission errors. Review the error details in the output to diagnose.

  • Invalid User URN
    Make sure the User URN includes the required prefix and is correctly formatted.

Links and References


If you need summaries for other resources or operations, feel free to ask!

Discussion