HDW LinkedIn icon

HDW LinkedIn

Integrate with Horizon Data Wave LinkedIn API
Join our community

Actions19

Overview

This node integrates with the Horizon Data Wave LinkedIn API to retrieve LinkedIn user information based on an email address. Specifically, the "Get User by Email" operation allows you to find LinkedIn users by providing their email addresses. This is useful in scenarios such as enriching contact data, verifying user identities, or gathering professional profiles linked to known emails.

For example, a sales team could input a list of email addresses to fetch corresponding LinkedIn profiles to better understand potential leads. Similarly, HR teams might verify candidate details by searching LinkedIn profiles via email.

Properties

Name Meaning
Email The email address to search for the LinkedIn user.
Count Maximum number of results to return (default is 5).
Timeout Timeout duration in seconds for the API request (default is 300 seconds).

Output

The output is a JSON object or an array of JSON objects representing LinkedIn user profiles found by the email search. Each item contains detailed user information as returned by the Horizon Data Wave LinkedIn API.

  • If multiple users match the email query (up to the specified count), each user profile is returned as a separate JSON object.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Horizon Data Wave LinkedIn API.
  • The base URL for API requests is https://api.horizondatawave.ai.
  • The node uses HTTP POST requests to the endpoint /api/linkedin/email/user with JSON payload containing the email and other parameters.

Troubleshooting

  • Common Issues:

    • Invalid or missing API authentication token will cause authentication errors.
    • Providing an invalid email format may result in no results or API errors.
    • Exceeding rate limits or token points quota can lead to throttling or errors.
    • Network timeouts if the timeout parameter is set too low or network issues occur.

  • Error Messages:

    • Errors include HTTP status codes and may contain headers like x-error, x-request-id, and x-execution-time for debugging.
    • Typical error messages might indicate API errors, HTTP status failures, or malformed requests.
    • To resolve, ensure valid credentials, correct email format, and appropriate timeout settings.
    • Use the provided error details and request IDs to contact support if needed.

Links and References

Discussion