HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API

Actions18

Overview

The "Sales Navigator Search" operation of the HDW LinkedIn node enables advanced user profile searches on LinkedIn using Sales Navigator filters. This operation allows users to perform highly targeted searches by specifying keywords and a variety of detailed filters such as names, titles, locations, industries, company details, languages, job functions, and more.

This node is beneficial for sales professionals, recruiters, marketers, and business developers who want to find specific LinkedIn profiles matching complex criteria to generate leads, recruit talent, or conduct market research.

Practical examples:

  • Finding decision-makers in a particular industry and location with specific job titles.
  • Searching for professionals who recently posted content on LinkedIn.
  • Filtering candidates by years of experience, company size, and language skills.

Properties

Name Meaning
Keywords Any keyword(s) to search within user profiles.
Count Maximum number of results to return (up to 2500).
Timeout Request timeout in seconds (range: 20 to 1500).
Additional Filters A collection of optional filters to refine the search:
- First Names Comma-separated list of exact first names to filter by.
- Last Names Comma-separated list of exact last names to filter by.
- Current Titles Comma-separated list of exact words to match in current job titles.
- Past Titles Comma-separated list of exact words to match in past job titles.
- Location Location name or URN to filter profiles by geographic area.
- Industry Industry name or URN to filter profiles by industry sector.
- Current Companies Current company name or URN to filter profiles by current employer.
- Past Companies Past company name or URN to filter profiles by previous employers.
- Education Education institution name or URN to filter profiles by educational background.
- Company Locations Company location name or URN to filter profiles by company geographic presence.
- Is Posted On LinkedIn Boolean flag to filter users who have recently published content on LinkedIn.
- Company Sizes Select one or multiple company size ranges (e.g., Self-Employed, 1-10, 11-50, etc.).
- Company Types Select one or multiple types of companies (e.g., Public Company, Privately Held, Non Profit, etc.).
- Languages Select one or multiple profile languages (e.g., English, Spanish, Chinese, etc.).
- Functions Select one or multiple job functions (e.g., Accounting, Marketing, Sales, Engineering, etc.).
- Levels Select one or multiple job levels (e.g., Entry, Director, CXO, Senior, etc.).
- Years in Current Company Select one or multiple ranges for years spent in the current company (e.g., 0-1, 1-2, 3-5, etc.).
- Years in Current Position Select one or multiple ranges for years spent in the current position (e.g., 0-1, 1-2, 3-5, etc.).

Output

The output JSON contains an array of user profile objects matching the search criteria. Each object represents a LinkedIn user profile returned by the Sales Navigator search API.

  • The structure of each profile object depends on the external API response but typically includes user identifiers, names, job titles, companies, locations, industries, and other relevant profile data.
  • The node does not output binary data; all data is returned as JSON.

Dependencies

  • Requires an active connection to the Horizon Data Wave LinkedIn API service.
  • Requires configuration of an API authentication credential (an API key or token) for the Horizon Data Wave LinkedIn API within n8n.
  • Network access to https://api.horizondatawave.ai must be available.

Troubleshooting

  • Common issues:

    • Exceeding the maximum allowed count (over 2500) may cause errors or truncated results.
    • Providing invalid or malformed filter values (e.g., incorrect URNs or badly formatted comma-separated lists) can lead to request failures.
    • Network connectivity or authentication failures will prevent successful API calls.

  • Error messages:

    • Errors from the API are returned with a message and possibly detailed error information.
    • If the node is set to continue on failure, errors are included in the output JSON under an error field with details.
    • To resolve errors, verify that all input parameters conform to expected formats and that the API credentials are valid and active.

Links and References

Discussion