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, for the User resource and the Get Profile (Me) operation, it retrieves the current LinkedIn user's profile information. This is useful when you want to fetch details about the authenticated user without needing to specify a user ID explicitly.

Common scenarios include:

  • Automatically obtaining the profile data of the connected LinkedIn account.
  • Using the profile information as part of a workflow that personalizes messages or posts.
  • Verifying the authenticated user's identity or profile details before performing other operations.

Example: You might use this node to get your own LinkedIn profile data and then use parts of that data to customize outreach messages or update CRM records.

Properties

Name Meaning
Timeout Timeout in seconds for the API request (default: 300)

Output

The output JSON contains the current LinkedIn user's profile data as returned by the Horizon Data Wave API. The exact structure depends on the API response but typically includes fields such as user identifiers, names, job titles, and other profile metadata.

If multiple items were returned (not typical for "Get Profile (Me)"), each would be an individual JSON object in the output array.

No binary data is output 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 https://api.horizondatawave.ai/api/linkedin/management/me.
  • Proper configuration of the API credentials within n8n is necessary.
  • Network access to the Horizon Data Wave API must be available.

Troubleshooting

  • No credentials provided!
    Error occurs if the API credentials are missing. Ensure you have configured the required API authentication token in n8n.

  • Account ID is missing in credentials!
    The API credentials must include an account identifier. Verify that the credentials contain this information.

  • Timeouts or slow responses
    Adjust the "Timeout" property to allow more time for the API call if network latency is high.

  • API errors with HTTP status codes
    The node captures detailed error information from the API response headers and body. Common issues may include invalid tokens, rate limits, or malformed requests. Review the error message and ensure your credentials and parameters are correct.

  • Continue On Fail option
    If enabled, the node will return error details in the output instead of stopping execution, which can help in debugging workflows.

Links and References

Discussion