Actions19
- User Actions
- Email Actions
- Post Actions
- Company Actions
- Search Actions
- Google Actions
- Group Actions
Overview
The "Get Company" operation of the HDW LinkedIn node allows users to retrieve detailed information about a specific company from LinkedIn via the Horizon Data Wave LinkedIn API. This operation is useful for scenarios where you want to enrich your workflows with company data such as company profile details, industry, size, or other metadata available on LinkedIn.
Practical examples include:
- Enriching CRM records with up-to-date LinkedIn company information.
- Automating market research by fetching company profiles based on aliases or URNs.
- Integrating company data into business intelligence dashboards.
Properties
| Name | Meaning |
|---|---|
| Company | The identifier of the company to fetch. It can be a company alias, URL, or URN (e.g., "openai" or "company:1441"). |
| Timeout | The maximum time in seconds to wait for the API response before timing out. Default is 300 seconds. |
Output
The output JSON contains the detailed LinkedIn company information returned by the API. This typically includes company profile data such as name, description, industry, size, location, and other relevant metadata provided by LinkedIn.
If multiple companies were requested (not applicable for this single "Get Company" operation), the output would be an array of company objects. For this operation, the output is a single JSON object representing the requested company's data.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API.
- Requires an API key credential configured in n8n for authentication with the Horizon Data Wave LinkedIn service.
- The base URL used for requests is
https://api.horizondatawave.ai. - The node sends POST requests to
/api/linkedin/companyendpoint with the specified company identifier.
Troubleshooting
- Timeouts: If the request times out, consider increasing the "Timeout" property value.
- Invalid Company Identifier: Ensure the "Company" input is correctly formatted as an alias, URL, or URN. Incorrect formats may result in errors or empty responses.
- API Errors: The node surfaces HTTP status codes and error messages from the API. Common issues include authentication failures (check API key validity) or rate limiting.
- Empty or Unexpected Response: Verify that the company exists on LinkedIn and that the API has access to its data.
- Continue On Fail: If enabled, errors will be returned as part of the output JSON instead of stopping execution, allowing workflows to handle errors gracefully.
Links and References
- Horizon Data Wave LinkedIn API Documentation (hypothetical link)
- LinkedIn Company Profiles
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
This summary is based on static analysis of the node's source code and input properties related to the "Company" resource and "Get Company" operation only.