Linked API icon

Linked API

Control your LinkedIn accounts and retrieve real-time data.

Actions27

Overview

The "Fetch Person in Sales Navigator" operation of the Linked API node allows users to retrieve detailed information about a specific person on LinkedIn Sales Navigator by providing their hashed LinkedIn URL. This is useful for automating workflows that require up-to-date professional data, such as lead enrichment, CRM updates, or personalized outreach campaigns.

Typical use cases include:

  • Automatically fetching profile details of leads identified in other systems.
  • Enriching contact records with real-time LinkedIn Sales Navigator data.
  • Triggering follow-up actions based on retrieved profile information.

Properties

Name Meaning
Webhook URL The URL where the response from the fetch operation will be sent via webhook.
Person Hashed URL The hashed LinkedIn URL of the person whose Sales Navigator profile you want to fetch.

Output

The node outputs JSON data containing the fetched person's profile information from LinkedIn Sales Navigator. This typically includes structured details such as name, current position, company, location, and other relevant professional attributes as provided by the Sales Navigator API.

If the node supports binary data output (not indicated here), it would represent any associated files or media related to the person’s profile.

Dependencies

  • Requires an API key credential for authenticating with the Linked API service.
  • Needs a valid webhook URL configured to receive asynchronous responses.
  • The node sends a POST request to https://api.linkedapi.io/automation/execute with the operation details.

Troubleshooting

  • Missing or invalid webhook URL: Ensure the webhook URL is correctly set and publicly accessible; otherwise, the node cannot deliver the response.
  • Invalid or malformed Person Hashed URL: Verify the hashed URL corresponds exactly to a LinkedIn Sales Navigator profile URL.
  • Authentication errors: Confirm that the API key credential is valid and has necessary permissions.
  • Timeouts or no response: Check network connectivity and webhook endpoint availability.
  • Error messages from API: Review the returned error details for issues like rate limits or invalid parameters.

Links and References

Discussion