Leadspicker Node icon

Leadspicker Node

Interact with Leadspicker API
Join our community

Actions14

Overview

This node integrates with the Leadspicker API to manage and retrieve data related to persons, projects, replies, company contacts, and LinkedIn activities. Specifically, for the Person resource with the List Persons operation, it fetches a paginated list of persons associated with a specified project.

Common scenarios where this node is beneficial include:

  • Retrieving contact lists from a specific project for marketing or sales outreach.
  • Automating workflows that require up-to-date person data from Leadspicker.
  • Integrating Leadspicker person data into CRMs or other business tools.

Practical example:

  • You have a project in Leadspicker representing a sales campaign. Using this node, you can list all persons linked to that project, paginate through results, and process them further in your workflow (e.g., sending emails or updating records).

Properties

Name Meaning
Project ID The numeric ID of the project from which to list persons.
Page The page number for pagination (default is 1).
Results Per Page Number of persons to return per page (default is 100).

Output

The output is a JSON array where each item represents a person retrieved from the Leadspicker API under the specified project. Each person object contains fields as returned by the /persons-simple endpoint of the API, typically including identifiers and basic person details.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Leadspicker API.
  • The node makes HTTP GET requests to the /persons-simple endpoint of the Leadspicker API.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Project ID will cause the API request to fail.
    • Pagination parameters out of range may result in empty responses.
    • Network or authentication errors if the API key is invalid or not configured.

  • Error messages:

    • "The operation "list" is not supported for Person resource." — This would indicate a misconfiguration or unsupported operation; ensure the operation is set correctly.
    • API errors related to authentication or rate limits should be resolved by verifying API credentials and usage limits.

Links and References

Discussion