Actions19
- User Actions
- Email Actions
- Post Actions
- Company Actions
- Search Actions
- Google Actions
- Group Actions
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 LinkedIn user identified by their unique User URN.
Typical use cases include:
- Gathering recent posts from a specific LinkedIn user for social media monitoring or analysis.
- Aggregating content shared by users for marketing insights or lead generation.
- Building dashboards or reports that display user activity on LinkedIn.
Example: You want to collect the last 10 posts from a LinkedIn user with URN fsd_profile:ACoAA... to analyze their content trends or engagement.
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 is a JSON array where each item represents a LinkedIn post retrieved for the specified user. Each post object contains all relevant post details as returned by the Horizon Data Wave LinkedIn API, such as post content, timestamps, metadata, and possibly engagement metrics.
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/posts. - 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: If the timeout is too low, increase the "Timeout" property.
- API rate limits or quota exceeded: The API may limit requests; monitor usage accordingly.
Error messages:
- Errors from the API will include HTTP status codes and error messages in the response headers and body.
- Typical errors might mention invalid parameters, unauthorized access, or server errors.
- To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error details in the output.
Links and References
- Horizon Data Wave LinkedIn API Documentation (general endpoint base URL)
- LinkedIn URN format reference (not provided here, but ensure URNs are correctly formatted)
This summary is based solely on static analysis of the provided source code and property definitions.