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 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 unique LinkedIn URN, enabling automated workflows that track company updates or gather data for reporting.

Properties

Name Meaning
Company URN The unique identifier of the LinkedIn company in URN 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 node outputs an array of JSON objects, each representing a post from the specified LinkedIn company. Each item contains the post details as returned by the Horizon Data Wave 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 https://api.horizondatawave.ai/api/linkedin/company/posts.
  • The API expects parameters including the company URN, count, and timeout.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Company URN: Ensure the URN is correctly formatted and corresponds to a LinkedIn company.
    • API timeouts: If the timeout is too low, requests may fail; consider increasing the timeout value.
    • Authentication errors: Verify that the API key credential is valid and has the required permissions.

  • Error Messages:

    • Errors include HTTP status codes and may contain headers like x-error describing the issue.
    • Typical messages might indicate invalid input, unauthorized access, or rate limiting.
    • To resolve, check the error details provided in the output and adjust parameters or credentials accordingly.
    • The node supports continuing on failure, which allows capturing error details in the output JSON for further handling.

Links and References

Discussion