Leadspicker Node icon

Leadspicker Node

Interact with Leadspicker API
Join our community

Actions14

Overview

The node interacts with the Leadspicker API to manage and update person records within projects. Specifically, the "Update Person" operation allows users to modify details of an existing person by their unique ID. This is useful in scenarios where contact information or related company/social profile data needs to be kept current, such as updating job titles, email addresses, or social media links for leads or contacts in a CRM workflow.

Practical examples:

  • Updating a lead’s email address after receiving new contact info.
  • Changing a person's job position or company details when they switch roles.
  • Adding custom fields to enrich the person’s profile with additional metadata.

Properties

Name Meaning
Person ID The unique identifier of the person to update (required).
Person Details Collection of personal attributes to update: Country, Email, First Name, Last Name, Position.
Company Details Collection of company-related attributes: Company Name, Company Website, Company LinkedIn URL.
Social Profiles Collection of social profile URLs: LinkedIn, Sales Navigator.
Custom Fields Multiple key-value pairs for any additional custom data fields to add or update.

Output

The node outputs JSON data representing the updated person record as returned by the Leadspicker API. This includes all the updated fields and any server-generated metadata. The output is structured as an array of JSON objects, each corresponding to an input item processed.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Leadspicker API.
  • The node uses HTTP methods (PATCH) to update person data via the Leadspicker REST endpoints.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Person ID will result in an error from the API.
    • Omitting required fields or sending empty strings may cause partial updates or errors.
    • Network or authentication failures can prevent successful updates.

  • Error messages:

    • "The operation "update" is not supported for Person resource." — indicates a misconfiguration or unsupported operation.
    • API errors typically relay back messages about invalid IDs or missing permissions; ensure the API key has proper access.

  • Resolution tips:

    • Verify the Person ID exists before attempting an update.
    • Ensure all required credentials are correctly set up in n8n.
    • Use the "Continue On Fail" option to handle individual item errors gracefully in batch operations.

Links and References

Discussion