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 and search operations. Specifically, for the Search Locations operation under the Search resource, it allows users to search for LinkedIn locations by name. This can be useful in scenarios where you want to find location identifiers or details for use in other LinkedIn queries or workflows, such as filtering user searches by location or targeting content geographically.
Practical examples include:
- Finding a list of cities or regions matching a partial location name.
- Retrieving location data to enrich user profiles or company information.
- Using location search results to refine recruitment or marketing campaigns based on geography.
Properties
| Name | Meaning |
|---|---|
Location Name (name) |
The name of the location to search for on LinkedIn (e.g., city or region name). Required. |
Count (count) |
Maximum number of location results to return. Defaults to 10. |
Timeout (timeout) |
Timeout duration in seconds for the API request. Defaults to 300 seconds. |
Output
The output is a JSON array containing location objects returned by the LinkedIn API matching the search criteria. Each item in the output corresponds to one location result with its associated data fields as provided by the API.
The node does not output binary data.
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/locations. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an empty or invalid location name may result in no results or API errors.
- Network timeouts if the timeout value is too low or network connectivity issues occur.
Error messages:
- Errors from the API are captured and returned with details including HTTP status, error headers, request ID, execution time, and token usage.
- If the node is set to continue on failure, error details are included in the output JSON; otherwise, the workflow execution stops with the error.
Resolution tips:
- Ensure the API key credential is correctly configured and valid.
- Provide a meaningful location name string.
- Adjust the timeout parameter if requests frequently time out.
- Check network connectivity and firewall settings.
Links and References
- Horizon Data Wave LinkedIn API Documentation (general reference, actual docs URL may vary)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)
This summary is based solely on static analysis of the provided source code and property definitions.