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 data. Specifically, for the Post resource and the Get Post Reposts operation, it fetches reposts (shares) of a specified LinkedIn post identified by its URN. This is useful when you want to analyze how widely a post has been shared or track engagement beyond direct comments and reactions.

Common scenarios:

  • Marketing teams tracking the spread of a LinkedIn post.
  • Social media analysts measuring content virality.
  • Sales or recruitment professionals monitoring post reach within their network.

Example:
You provide the URN of a LinkedIn post, specify how many reposts you want to retrieve (e.g., 10), and optionally set a timeout. The node returns a list of repost activities related to that post.

Properties

Name Meaning
Post URN The unique identifier of the LinkedIn post to query reposts for. Must include prefix, e.g., activity:7234173400267538433.
Count Maximum number of repost results to return.
Timeout Timeout in seconds for the API request before aborting.

Output

The output is a JSON array where each item represents a repost of the specified LinkedIn post. Each repost object contains details about the repost activity as 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 https://api.horizondatawave.ai/api/linkedin/post/reposts.
  • The API expects JSON body parameters including the post URN, count, and timeout.
  • Proper configuration of the API credential in n8n is necessary for authentication.

Troubleshooting

  • Invalid or missing Post URN: Ensure the URN includes the required prefix (e.g., activity:). Without a valid URN, the API will reject the request.
  • Timeout errors: If the API call times out, consider increasing the timeout property value.
  • API rate limits or quota exceeded: The API may return errors if usage limits are hit. Check your API plan and usage.
  • Authentication failures: Verify that the API key credential is correctly configured and active.
  • Unexpected API responses: Inspect error details returned in the output if continueOnFail is enabled; these include HTTP status, error messages, and request IDs for support.

Links and References

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

Discussion