HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API
Join our community

Actions19

Overview

This node integrates with the Horizon Data Wave LinkedIn API to retrieve various types of LinkedIn user data. Specifically, for the User resource and Get Reactions operation, it fetches reactions made by a LinkedIn user identified by their User URN.

Typical use cases include:

  • Analyzing engagement on a user's LinkedIn content by retrieving who reacted to their posts.
  • Gathering social interaction metrics for personal or business insights.
  • Building dashboards or reports that summarize user activity on LinkedIn.

For example, you might input a LinkedIn User URN and request up to 10 recent reactions they have made, which can then be used to understand their interaction patterns or influence.

Properties

Name Meaning
User URN The unique identifier of the LinkedIn user whose reactions you want to retrieve. Must include prefix (e.g., fsd_profile:ACoAA...).
Count Maximum number of reaction results to return. Default is 10.
Timeout Timeout in seconds for the API request. Default is 300 seconds.

Output

The output is a JSON array where each item represents a reaction made by the specified user. Each JSON object contains details about an individual reaction, such as the type of reaction, the post or content it was made on, timestamps, and possibly other metadata returned by the Horizon Data Wave LinkedIn API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Horizon Data Wave LinkedIn API.
  • The node makes HTTP POST requests to the endpoint:
    https://api.horizondatawave.ai/api/linkedin/user/reactions
  • The API expects JSON bodies containing the User URN, count, and timeout parameters.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing User URN: Ensure the URN includes the correct prefix and is valid.
    • API timeouts: If the timeout is too low, increase the "Timeout" property to allow more time for the API response.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Rate limiting or quota exceeded: The API may limit requests; check error messages for token points or rate limit headers.

  • Error messages:

    • Errors from the API are captured and returned with details including HTTP status, API error message, request ID, execution time, and token points.
    • If the node is configured to continue on failure, these errors will appear in the output JSON under an error field.
    • To resolve errors, review the detailed error information and adjust inputs or credentials accordingly.

Links and References

  • Horizon Data Wave LinkedIn API documentation (refer to your API provider's official docs)
  • n8n HTTP Request node documentation for understanding API calls and authentication
  • LinkedIn URN format guidelines (to ensure correct User URN formatting)

Discussion