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 User resource and the Get User Comments operation, it fetches comments made by a specified LinkedIn user.

Use cases include:

  • Monitoring user engagement by retrieving comments a user has made on LinkedIn.
  • Analyzing user interaction patterns or sentiment based on their comments.
  • Aggregating user-generated content for marketing or research purposes.

For example, you can input a LinkedIn user's URN and get up to a specified number of their recent comments, optionally filtering comments created after a certain timestamp.

Properties

Name Meaning
User URN The unique identifier of the LinkedIn user whose comments you want to retrieve. Must include prefix (e.g., fsd_profile:ACoAA...).
Count Maximum number of comment results to return.
Timeout Timeout duration in seconds for the API request.
Commented After Optional filter to only include comments created after this Unix timestamp (in seconds).

Output

The node outputs an array of JSON objects, each representing a single comment made by the specified user. Each comment object contains details as returned by the Horizon Data Wave LinkedIn API, such as comment text, creation timestamp, and possibly metadata about the post or context where the comment was made.

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/user/comments.
  • Proper configuration of the API authentication within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing User URN: Ensure the URN includes the correct prefix and is valid.
    • API timeouts: Adjust the "Timeout" property if requests take too long or fail due to network latency.
    • Rate limiting or quota exceeded errors from the API.

  • Error messages:

    • Errors may include HTTP status codes and API error messages returned in headers or response body.
    • If the node fails, it provides detailed error information including HTTP status, API error message, request ID, execution time, and token usage points.

  • Resolution tips:

    • Verify API credentials are correctly set up.
    • Check that the User URN is accurate.
    • Increase timeout if needed.
    • Handle errors gracefully by enabling "Continue On Fail" in the node settings to avoid workflow interruption.

Links and References

Discussion