HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API

Actions18

Overview

This node integrates with the Horizon Data Wave LinkedIn API to retrieve various types of LinkedIn data. Specifically, for the User resource and Get Posts operation, it fetches posts made by a specified LinkedIn user identified by their URN (Uniform Resource Name). This is useful for scenarios where you want to analyze or display recent content shared by a LinkedIn user, such as monitoring social media activity, gathering content for marketing insights, or aggregating posts for reporting.

Practical example:
You can use this node to pull the latest 10 posts from a LinkedIn influencer or company representative to analyze engagement trends or curate content for newsletters.

Properties

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

Output

The output contains a JSON array of post objects retrieved from the LinkedIn user’s feed. Each item in the output corresponds to one post with its associated metadata as returned by the Horizon Data Wave LinkedIn API. The exact structure depends on the API response but typically includes fields like post content, creation date, author details, and engagement metrics.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Horizon Data Wave LinkedIn API.
  • Requires configuration of an API authentication token credential within n8n to authorize requests.
  • The base URL used for API calls is https://api.horizondatawave.ai.

Troubleshooting

  • Common issues:

    • Invalid or missing User URN: Ensure the URN is correctly formatted and includes the required prefix.
    • API timeouts: If the timeout is too low, increase the "Timeout" property to allow more time for the API to respond.
    • Authentication errors: Verify that the API key or token credential is correctly configured and has sufficient permissions.

  • Error messages:

    • "error": "Unauthorized": Indicates invalid or missing API credentials. Reconfigure the API authentication token.
    • "error": "User not found": The provided User URN does not correspond to any user. Double-check the URN value.
    • "error": "Request timed out": Increase the timeout setting or check network connectivity.

When Continue On Fail is enabled, errors are returned as part of the output JSON with error message and details.

Links and References

Discussion