Actions18
- Company Actions
- Search Actions
- Google Actions
- Group Actions
- User Actions
- Email Actions
- Post 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 Google - Search Companies operation, it allows users to search for LinkedIn companies using Google search queries based on specified company keywords.
Typical use cases include:
- Finding LinkedIn company profiles related to specific keywords or industries.
- Gathering company information for market research or lead generation.
- Enriching datasets with company URNs (unique resource names) for further LinkedIn API calls.
For example, a user might input keywords like "artificial intelligence, cloud computing" to retrieve LinkedIn companies related to these fields, optionally including their unique identifiers (URNs).
Properties
| Name | Meaning |
|---|---|
| Keywords | Company keywords for search, provided as a comma-separated string. |
| Include URNs | Boolean flag indicating whether to include URNs in the response; enabling this increases execution time. |
| Results Per Keyword | Maximum number of results to return per keyword; valid range is 1 to 10. |
| Timeout | Timeout duration in seconds for the API request. |
Output
The node outputs JSON data containing the search results from the Horizon Data Wave LinkedIn API. Each item in the output array corresponds to a company matching one of the provided keywords.
- The JSON structure includes company details as returned by the API.
- If "Include URNs" is enabled, the response will also contain unique resource names (URNs) for each company.
- No binary data is output by this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API service.
- An API key credential for authenticating requests to the Horizon Data Wave LinkedIn API must be configured in n8n.
- Network access to
https://api.horizondatawave.aiis necessary.
Troubleshooting
- Timeouts: If the operation takes too long, consider increasing the timeout property or reducing the number of results per keyword.
- Empty Results: Ensure that the keywords are correctly formatted and relevant to existing LinkedIn companies.
- API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Rate Limits: Excessive requests may trigger rate limiting; implement delays between executions if needed.
Common error messages include:
"error": "Authentication failed": Check API credentials."error": "Request timed out": Increase the timeout setting."error": "No detailed error information available": This generic message indicates an unknown failure; check network connectivity and API status.
Links and References
- Horizon Data Wave LinkedIn API Documentation (hypothetical link based on base URL)
- n8n HTTP Request Node Documentation
- LinkedIn Company Profiles Overview
Note: Internal credential type names and other internal identifiers have been generalized to comply with best practices.