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 comments on a specific LinkedIn post. It allows users to fetch and analyze comments made on posts identified by their unique URN (Uniform Resource Name). This is useful for social media analysts, marketers, or recruiters who want to monitor engagement, sentiment, or discussions around particular LinkedIn posts.

Practical examples include:

  • Gathering user feedback or opinions from comments on a company announcement post.
  • Monitoring discussions on a job posting to understand candidate interest.
  • Collecting comments for sentiment analysis or customer support follow-up.

Properties

Name Meaning
Post URN The unique identifier of the LinkedIn post, including prefix (e.g., activity:7234173400267538433).
Sort The sorting order of the comments. Options: Relevance (default) or Recent.
Count Maximum number of comment results to return (default is 10).
Timeout Timeout duration in seconds for the API request (default is 300 seconds).

Output

The output is a JSON array where each item represents a comment on the specified LinkedIn post. Each comment object contains details such as the comment text, author information, timestamps, and other metadata provided by the 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 /api/linkedin/post/comments on the base URL https://api.horizondatawave.ai.
  • Proper configuration of the API authentication within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Post URN: Ensure the URN includes the correct prefix and is valid.
    • API timeouts: If the request times out, consider increasing the Timeout property.
    • Rate limiting or quota exceeded errors from the API.

  • Error messages:

    • Errors returned from the API will include HTTP status codes and may contain headers like x-error, x-request-id, and x-execution-time for debugging.
    • If the node is set to continue on failure, error details are included in the output JSON under an error field.

  • Resolution tips:

    • Verify the Post URN format.
    • Check API key validity and permissions.
    • Adjust timeout settings if network latency is high.
    • Review API usage limits and ensure you have sufficient quota.

Links and References

Discussion