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 detailed LinkedIn user profile information. Specifically, the User - Get Profile operation fetches a LinkedIn user's profile by their alias, URL, or URN, optionally including their experience, education, and skills data.

This node is useful in scenarios such as:

  • Enriching CRM or marketing databases with detailed LinkedIn profile data.
  • Automating recruitment workflows by gathering candidate profiles.
  • Building analytics dashboards that require comprehensive user professional information.

For example, you can input a LinkedIn user alias and get back their full profile including work experience, educational background, and listed skills, enabling deeper insights into the user's professional history.

Properties

Name Meaning
User The LinkedIn user identifier; can be an alias, URL, or URN of the user whose profile is fetched.
Include Experience Boolean flag indicating whether to include the user's work experience information.
Include Education Boolean flag indicating whether to include the user's education information.
Include Skills Boolean flag indicating whether to include the user's skills information.

Output

The output is a JSON object representing the LinkedIn user's profile data as returned by the Horizon Data Wave LinkedIn API. This includes fields such as personal details, work experience, education history, and skills depending on the selected options.

If multiple items are processed, the output will be an array of such JSON objects, each corresponding to one user profile.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Horizon Data Wave LinkedIn API.
  • The node makes authenticated HTTP POST requests to https://api.horizondatawave.ai/api/linkedin/user.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing user identifier (alias/URL/URN) will cause the API to return errors.
    • Network or authentication failures may occur if the API key is invalid or expired.
    • Rate limiting or quota exceeded errors from the API could interrupt execution.

  • Error messages:

    • Errors include HTTP status codes and may contain headers like x-error describing the issue.
    • The node captures detailed error info including request ID and execution time when available.
    • To handle errors gracefully, enable "Continue On Fail" in the node settings to receive error details in output instead of stopping execution.

  • Resolution tips:

    • Verify the correctness of the user identifier input.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and API service status.
    • Use smaller request counts or increase timeout if facing rate limits or timeouts.

Links and References

Discussion