Leadspicker Node icon

Leadspicker Node

Interact with Leadspicker API
Join our community

Actions14

Overview

This node interacts with the Leadspicker API to manage "Person" entities among other resources. Specifically, for the Delete Person operation, it deletes a person record identified by a unique ID from the Leadspicker system.

Common scenarios where this node is beneficial include:

  • Cleaning up outdated or incorrect person records in your Leadspicker projects.
  • Automating data management workflows that require removing contacts no longer relevant.
  • Integrating with CRM or marketing automation systems to keep contact lists synchronized and accurate.

For example, you might use this node in an automation that removes persons who have unsubscribed or are no longer prospects, ensuring your project data stays current.

Properties

Name Meaning
Person ID The unique numeric ID of the person to delete

Output

The output JSON contains the response from the Leadspicker API after attempting to delete the specified person. Typically, this will be an object indicating success or failure of the deletion request. The exact structure depends on the API but usually includes status information or confirmation.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
  • The node uses HTTP requests to communicate with the Leadspicker service endpoints.
  • Proper permissions on the API key are necessary to perform delete operations on person records.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Person ID will likely result in an error from the API.
    • Network connectivity problems can cause request failures.
    • Insufficient API permissions may prevent deletion.

  • Error messages:

    • "The operation "delete" is not supported for Person resource." — This would indicate a misconfiguration or unsupported operation; ensure the operation parameter is correctly set to "delete".
    • API errors related to authorization or missing person ID will be returned as error messages; verify credentials and input parameters.

  • Resolution tips:

    • Double-check the Person ID value is correct and exists in the target project.
    • Confirm the API key has delete permissions.
    • Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite individual item errors.

Links and References

Discussion