Leadspicker Node icon

Leadspicker Node

Interact with Leadspicker API
Join our community

Actions14

Overview

The node interacts with the Leadspicker API to manage and retrieve information about persons, projects, replies, and LinkedIn activities. Specifically for the Person resource with the Get Person operation, it fetches detailed information about a person by their unique ID.

This node is beneficial in scenarios where you need to integrate Leadspicker's contact data into your workflows, such as enriching CRM records, automating outreach processes, or syncing contact details across systems.

Example use case:
You have a workflow that triggers when a new lead is added, and you want to fetch detailed information about that lead (person) from Leadspicker by their ID to enrich your database or trigger personalized communications.

Properties

Name Meaning
Person ID The unique numeric identifier of the person to retrieve. This is required for the Get Person operation.

Output

The output is a JSON object representing the person's data retrieved from the Leadspicker API. It typically includes fields such as:

  • Personal details (e.g., first name, last name, email, country, position)
  • Company details (e.g., company name, website, LinkedIn URL)
  • Social profiles (e.g., LinkedIn, Sales Navigator URLs)
  • Custom fields if any were set on the person record

The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Leadspicker API.
  • The node makes HTTP requests to Leadspicker endpoints to perform operations.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Person ID will likely result in an error or empty response.
    • Network connectivity issues can cause request failures.
    • Missing or incorrect API credentials will prevent successful API calls.

  • Error messages:

    • "The operation "get" is not supported for Person resource." — This would indicate an internal misconfiguration; ensure the operation parameter is correctly set to "get".
    • API errors returned from Leadspicker (e.g., 404 Not Found if the person ID does not exist).

  • Resolutions:

    • Verify the Person ID is correct and exists in Leadspicker.
    • Check API credentials and permissions.
    • Ensure network access to Leadspicker API endpoints.

Links and References

Discussion