EspoCRM icon

EspoCRM

Interact with EspoCRM API

Actions25

Overview

This node integrates with the EspoCRM API to manage CRM data entities. Specifically, for the Contact resource and the Delete operation, it deletes a contact record identified by its unique Contact ID. This is useful in scenarios where you need to programmatically remove outdated or incorrect contact information from your CRM system.

Practical examples include:

  • Automatically deleting contacts that unsubscribe from marketing campaigns.
  • Cleaning up test or duplicate contact records during data maintenance workflows.
  • Removing contacts as part of GDPR compliance processes when users request data deletion.

Properties

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

Output

The output is a JSON array containing an object for each processed input item. For the Delete operation on a Contact, the output object has the following structure:

{
  "success": true,
  "id": "contactIdValue",
  "entityType": "contact"
}
  • success: A boolean indicating whether the deletion was successful.
  • id: The Contact ID of the deleted record.
  • entityType: The resource type, here always "contact".

No binary data is output by this node.

Dependencies

  • Requires an active connection to an EspoCRM instance via its REST API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses internal helper functions to send HTTP DELETE requests to the EspoCRM API endpoint corresponding to the contact entity.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will cause the API to reject the deletion request.
    • Network connectivity problems or incorrect API credentials will result in authentication or connection errors.
    • Attempting to delete a non-existent contact may return an error or no-op response depending on EspoCRM API behavior.

  • Error messages:

    • "The operation "delete" is not supported for resource type "contact": This would indicate a misconfiguration or unsupported operation, but per code, delete is supported for contact.
    • API errors returned from EspoCRM (e.g., 404 Not Found if contact does not exist) will be surfaced as node execution errors unless "Continue On Fail" is enabled.

  • Resolution tips:

    • Verify the Contact ID is correct and exists in EspoCRM.
    • Ensure API credentials are valid and have sufficient permissions.
    • Check network access to the EspoCRM server.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion