HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API

Actions18

Overview

The "Get Company" operation of the HDW LinkedIn node retrieves detailed information about a specific company from the Horizon Data Wave LinkedIn API. This node is useful for workflows that require enriched company data such as company profiles, industry details, or other metadata associated with a company on LinkedIn.

Typical use cases include:

  • Enriching CRM records with up-to-date company information.
  • Market research and competitive analysis by fetching company details.
  • Automating business intelligence processes that involve company data aggregation.

For example, you can input a company alias like "openai" or a company URN such as "company:1441" to fetch comprehensive LinkedIn data about that company.

Properties

Name Meaning
Company The identifier of the company to retrieve. 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 is a JSON object containing the detailed LinkedIn company information returned by the API. The structure depends on the API response but typically includes fields such as company name, description, industry, size, location, and other relevant metadata.

If multiple companies were requested (not applicable for this single-company operation), the output would be an array of such objects. Since this operation targets one company, the output is a single JSON object per execution item.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Horizon Data Wave LinkedIn API.
  • An API authentication token or API key credential must be configured in n8n under the node's credentials settings.
  • The base URL used for requests is https://api.horizondatawave.ai.
  • The node sends HTTP POST requests to the endpoint /api/linkedin/company with the specified parameters.

Troubleshooting

  • Timeouts: If the request times out, consider increasing the "Timeout" property value.
  • Invalid Company Identifier: Ensure the "Company" property is correctly formatted as an alias, URL, or URN. Incorrect formats may cause errors or empty responses.
  • Authentication Errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • API Rate Limits: Frequent calls might hit rate limits imposed by the API; implement delays or retries if necessary.
  • Error Messages: On failure, the node returns an error message and may include detailed error information from the API response. Review these details to diagnose issues.

Links and References

Discussion