HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API

Actions18

Overview

This node integrates with the Horizon Data Wave LinkedIn API to perform various LinkedIn-related data retrieval and search operations. Specifically, the Search Locations operation allows users to search for LinkedIn locations by name, returning a list of matching location entities.

Common scenarios where this node is beneficial include:

  • Enriching CRM or marketing databases with LinkedIn location data.
  • Filtering or segmenting LinkedIn user or company data based on geographic locations.
  • Automating workflows that require location-based LinkedIn insights.

For example, a user might input a city or region name to retrieve LinkedIn-recognized locations for targeted outreach or analysis.

Properties

Name Meaning
Location Name (name) The name of the location to search for (e.g., "San Francisco", "New York"). This is a required string input.
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 node outputs an array of JSON objects representing LinkedIn locations matching the search criteria. Each item in the output corresponds to one location entity returned by the API.

  • The json field contains the location data as provided by the Horizon Data Wave LinkedIn API.
  • There is no binary data output for this operation.

Dependencies

  • Requires an active connection to the Horizon Data Wave LinkedIn API.
  • Users must configure the node with a valid API authentication token (an API key credential) for the Horizon Data Wave service.
  • The base URL used for requests is https://api.horizondatawave.ai.

Troubleshooting

  • Timeouts: If the request times out, consider increasing the Timeout property value.
  • No Results: Ensure the Location Name is spelled correctly and is recognized by LinkedIn.
  • Authentication Errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • API Rate Limits: If many requests are made in quick succession, the API may throttle requests; use delays between executions if needed.

Common error messages include:

  • "error": "Unauthorized" — indicates invalid or missing API credentials.
  • "error": "Request timed out" — suggests increasing the timeout or checking network connectivity.
  • "error": "No detailed error information available" — generic fallback error; check API response details or logs.

Links and References

Discussion