Klipy icon

Klipy

Interact with Klipy CRM API to manage contacts, companies, and interactions. Can be used as an AI tool for CRM operations.
Join our community

Actions13

Overview

This node integrates with the Klipy CRM API to manage "Person" records, including deleting a person by their ID. The "Delete Person" operation removes a specified person from the CRM database using their unique identifier.

Common scenarios for this node include:

  • Automating cleanup of outdated or incorrect contact records.
  • Removing contacts who have opted out or are no longer relevant.
  • Integrating with workflows that synchronize external data sources and need to delete persons in Klipy CRM accordingly.

Example use case: Automatically delete a person record when they unsubscribe from a mailing list or when a related business process marks them as inactive.

Properties

Name Meaning
Person ID The unique identifier of the person to delete. This is required to specify which person record should be removed.

Output

The node outputs the JSON response returned by the Klipy CRM API after attempting to delete the person. This typically includes confirmation of deletion or details about the deleted record.

The output structure is an array of JSON objects representing the API response(s). If multiple inputs are processed, each result is included in the array.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Klipy CRM API.
  • The base URL for the Klipy API must be configured in the credentials.
  • Uses HTTP DELETE requests to the endpoint /people/{personId}.

Troubleshooting

  • Missing or invalid Person ID: The operation requires a valid person ID. Ensure the "Person ID" property is provided and correctly references an existing person.
  • Authentication errors: If the API key or base URL is missing or incorrect, the node will fail. Verify the API key credential and base URL configuration.
  • API errors on deletion: The API may return errors if the person does not exist or cannot be deleted due to dependencies. Check the error message returned by the API for details.
  • Network issues: Connectivity problems can cause request failures. Confirm network access to the Klipy API endpoint.

If the node is set to continue on failure, errors will be included in the output as error messages instead of stopping execution.

Links and References

Discussion