Actions19
- User Actions
- Email Actions
- Post Actions
- Company Actions
- Search Actions
- Google Actions
- Group Actions
Overview
This node integrates with the Horizon Data Wave LinkedIn API to perform various LinkedIn-related data retrieval operations. Specifically, for the User resource and Search operation, it allows searching for LinkedIn users based on keywords and multiple optional filters such as name, title, company, location, industry, and education.
Common scenarios where this node is beneficial include:
- Recruiting professionals by searching for candidates matching specific criteria.
- Market research by identifying professionals in certain industries or companies.
- Sales prospecting by finding potential leads with particular job titles or company affiliations.
For example, a user can search for "software engineer" profiles located in "San Francisco" working at a specific company, limiting results to 50 users, with a timeout of 300 seconds.
Properties
| Name | Meaning |
|---|---|
| Keywords | Any keyword(s) to search within user profiles (e.g., "software engineer"). |
| Count | Maximum number of results to return (maximum 1000). |
| Timeout | Timeout duration in seconds for the search request (range: 20-1500 seconds). |
| Additional Fields | Optional filters to refine the search: |
| - First Name | Exact first name of the user. |
| - Last Name | Exact last name of the user. |
| - Title | Exact word in the user's job title. |
| - Company Keywords | Exact word(s) in the company name. |
| - School Keywords | Exact word(s) in the school name. |
| - Current Company | Current company URN or name. |
| - Past Company | Past company URN or name. |
| - Location | Location name or URN (geographical identifier). |
| - Industry | Industry URN or name. |
| - Education | Education URN or name. |
Output
The node outputs an array of JSON objects representing LinkedIn user profiles that match the search criteria. Each item in the output corresponds to one user profile returned by the API.
The exact structure of each user object depends on the API response but typically includes fields such as user identifiers, names, job titles, companies, locations, and other profile details.
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/search/users. - Proper configuration of the API authentication in n8n is necessary.
- Network connectivity to the external API endpoint is required.
Troubleshooting
- Timeouts: If the search takes too long, consider increasing the
Timeoutproperty within allowed limits or reducing theCountof results requested. - API Errors: Errors from the API may include HTTP status codes and error messages. Common issues include invalid credentials, exceeding rate limits, or malformed parameters.
- Empty Results: Ensure that the keywords and additional filters are correctly specified; overly restrictive filters may yield no results.
- Invalid Parameter Values: For example, setting
Countabove 1000 will likely cause errors; adhere to documented limits. - Network Issues: Verify network access to the API endpoint and correct API key usage.
If the node encounters an error and Continue On Fail is enabled, it returns detailed error information including HTTP status, API error message, request ID, execution time, and token points used.
Links and References
- Horizon Data Wave LinkedIn API Documentation (Assumed URL based on baseURL)
- LinkedIn Profile Search Concepts
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
This summary is based solely on static analysis of the provided source code and input property definitions.