Actions18
- Company Actions
- Search Actions
- Google Actions
- Group Actions
- User Actions
- Email Actions
- Post Actions
Overview
This node integrates with the Horizon Data Wave LinkedIn API to retrieve comments on a specific LinkedIn post. It is useful for scenarios where you want to analyze engagement, gather feedback, or monitor discussions related to a particular LinkedIn post. For example, marketers can use it to collect user comments for sentiment analysis, recruiters might track candidate interactions, or social media managers could monitor community responses.
The operation "Get Post Comments" fetches comments on a LinkedIn post identified by its URN (Uniform Resource Name). It supports sorting comments by relevance or recency and allows limiting the number of results returned.
Properties
| Name | Meaning |
|---|---|
| Post URN | The unique identifier of the LinkedIn post, including its prefix (e.g., activity:7234173400267538433). This specifies which post's comments to retrieve. |
| Sort | The order in which to sort the comments. Options are: 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 node outputs an array of JSON objects, each representing a comment on the specified LinkedIn post. Each comment object contains details as provided by the Horizon Data Wave LinkedIn API, typically including the comment text, author information, timestamps, and possibly metadata about likes or replies.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API.
- An API key credential for authenticating requests to the Horizon Data Wave service must be configured in n8n.
- The node sends HTTP POST requests to the endpoint
/api/linkedin/post/commentson the base URLhttps://api.horizondatawave.ai.
Troubleshooting
- Invalid or missing Post URN: Ensure the Post URN includes the correct prefix and is valid. Errors may occur if the URN is malformed or does not correspond to an existing post.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Timeouts: If the request times out, consider increasing the timeout property or checking network connectivity.
- Empty results: If no comments are returned, confirm that the post actually has comments and that the count parameter is set appropriately.
- Rate limits or API errors: The API may return error messages if rate limits are exceeded or if there are internal server issues. Review error details in the node output for guidance.
Links and References
- Horizon Data Wave LinkedIn API Documentation (generic link, replace with actual if available)
- LinkedIn Post URN Format Explanation (for understanding URNs)
Note: This summary is based solely on static code analysis and property definitions without runtime execution.