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 information about employees of one or more LinkedIn companies. Specifically, the "Get Company Employees" operation allows users to fetch employee data by specifying company URNs and optional search filters such as keywords, first name, and last name. This is useful for scenarios like talent acquisition, market research, or competitive analysis where you want to gather detailed employee information from specific companies on LinkedIn.

For example, a recruiter could input a list of company URNs to get a curated list of employees matching certain criteria (e.g., keyword in profile, exact first or last name) to identify potential candidates.

Properties

Name Meaning
Companies Comma-separated list of LinkedIn company URNs (e.g., "company:14064608,company:1441") to query.
Keywords Optional keywords to filter employees by any matching text in their profiles.
First Name Optional exact first name to filter employees.
Last Name Optional exact last name to filter employees.
Count Maximum number of employee results to return (default 10).
Timeout Timeout in seconds for the API request (default 300 seconds).

Output

The output is an array of JSON objects, each representing an employee matching the specified criteria from the given companies. The structure of each employee object depends on the API response but typically includes details such as name, position, company affiliation, and other LinkedIn profile data.

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 authenticated HTTP POST requests to https://api.horizondatawave.ai/api/linkedin/company/employees.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or malformed company URNs may result in empty or error responses.
    • Exceeding the maximum allowed count or timeout values might cause request failures.
    • Network issues or incorrect API credentials will lead to authentication errors.

  • Error Messages:

    • Errors returned from the API include HTTP status codes and may contain headers with additional error details.
    • If the node is set to continue on failure, error details are included in the output JSON under fields like error, details, httpStatus, and apiError.
    • To resolve errors, verify that company URNs are correct, ensure the API key is valid, and check network connectivity.

Links and References

Discussion