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 posts made by a specified LinkedIn company. It is useful for scenarios where you want to monitor or analyze recent content published by a company on LinkedIn, such as marketing analysis, competitive intelligence, or social media monitoring.
For example, you can use this node to fetch the latest 10 posts from a company identified by its URN (Uniform Resource Name), enabling automated workflows that track company updates or gather data for reporting.
Properties
| Name | Meaning |
|---|---|
| Company URN | The unique identifier of the company in LinkedIn format (e.g., "company:11130470"). Only company URN type is allowed. |
| Count | Maximum number of posts to retrieve. Defaults to 10. |
| Timeout | Timeout duration in seconds for the API request. Defaults to 300 seconds. |
Output
The output contains an array of JSON objects, each representing a post from the specified LinkedIn company. Each item in the output corresponds to one post's data as returned by the Horizon Data Wave LinkedIn API.
- The
jsonfield holds the post details. - There is no binary data output for this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API.
- Requires configuration of an API authentication token credential within n8n to authenticate requests to the external service.
- The base URL used for API calls is
https://api.horizondatawave.ai.
Troubleshooting
- Invalid Company URN: If the provided company URN is not in the correct format (e.g., missing the "company:" prefix), the API may return an error or no results. Ensure the URN is correctly formatted.
- Timeouts: If the timeout value is too low, requests might fail due to network latency or server processing time. Increase the timeout if you encounter timeout errors.
- API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly configured in n8n.
- Empty Results: If no posts are returned, verify that the company has recent posts and that the URN is correct.
Links and References
- Horizon Data Wave LinkedIn API Documentation (general reference, actual docs URL may vary)
- LinkedIn URN Format Explanation (for understanding URNs)
If you need further details about other operations or resources, feel free to ask!