HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API

Actions18

Overview

This node integrates with the Horizon Data Wave LinkedIn API to retrieve employee statistics for a specified LinkedIn company. It is useful for gaining insights into the composition and characteristics of a company's workforce as represented on LinkedIn. Typical use cases include HR analytics, market research, competitive analysis, and business intelligence where understanding employee demographics or trends within a company is valuable.

For example, you can input a company's unique LinkedIn URN (Uniform Resource Name) to fetch aggregated employee data such as counts by department, seniority, location, or other available statistics provided by the API.

Properties

Name Meaning
Company URN The unique identifier of the company on LinkedIn, including the prefix (e.g., "company:79111745"). This specifies which company's employee stats to retrieve.
Timeout The maximum time in seconds to wait for the API response before timing out. Default is 300 seconds.

Output

The node outputs JSON data containing the employee statistics of the specified LinkedIn company. The exact structure depends on the API response but typically includes aggregated metrics about employees such as distribution by roles, locations, seniority levels, or other demographic or organizational attributes.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Horizon Data Wave LinkedIn API.
  • Requires an API authentication token configured in n8n credentials for this service.
  • The base URL used for requests is https://api.horizondatawave.ai.
  • The node sends POST requests to the endpoint /api/linkedin/company/employee_stats with the company URN and timeout parameters.

Troubleshooting

  • Timeouts: If the request takes longer than the specified timeout, it may fail. Increase the timeout property if necessary.
  • Invalid Company URN: Ensure the company URN is correctly formatted and includes the required prefix (e.g., "company:").
  • Authentication Errors: Verify that the API key credential is valid and has the necessary permissions.
  • API Rate Limits: Excessive requests may be throttled by the API; consider adding delays between executions or reducing request frequency.
  • Error Responses: If the API returns an error, the node will output an error message with details if "Continue On Fail" is enabled; otherwise, it will throw an error.

Links and References

Discussion