EspoCRM icon

EspoCRM

Interact with EspoCRM API

Actions25

Overview

This node integrates with the EspoCRM API to manage various CRM resources, including custom entities. Specifically, for the Custom Entity - Delete operation, it deletes a record of a specified custom entity type by its record ID. This is useful when you need to programmatically remove obsolete or incorrect records from your EspoCRM instance.

Common scenarios include:

  • Automating cleanup of outdated customer data.
  • Removing test or temporary records after processing.
  • Integrating deletion workflows triggered by external events or conditions.

Example: Automatically delete a "Case" custom entity record when a related support ticket is closed in another system.

Properties

Name Meaning
Entity Type Name or ID The type of custom entity to interact with (e.g., Opportunity, Case, Product). Choose from a list or specify an ID via expression.
Record ID The unique identifier of the record to delete within the specified custom entity type.

Output

The output JSON array contains one object per input item processed. For the delete operation on a custom entity, each output object has the following structure:

{
  "success": true,
  "id": "<record ID>",
  "entityType": "<custom entity type>"
}
  • success: Indicates whether the deletion was successful (true).
  • id: The ID of the deleted record.
  • entityType: The type of the custom entity from which the record was deleted.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to an EspoCRM instance via an API key or authentication token configured in n8n credentials.
  • The node depends on EspoCRM's REST API being accessible and properly configured.
  • The "Entity Type Name or ID" options are dynamically loaded from the EspoCRM metadata service.

Troubleshooting

  • Common issues:

    • Invalid or missing record ID: The node requires a valid record ID; ensure the ID exists in EspoCRM.
    • Incorrect entity type: Selecting an unsupported or misspelled entity type will cause errors.
    • API connectivity problems: Network issues or invalid credentials will prevent successful deletion.

  • Error messages:

    • "The operation "delete" is not supported for resource type "customEntity": This indicates a misconfiguration or unsupported operation; verify the selected resource and operation.
    • API errors returned from EspoCRM (e.g., 404 Not Found) usually mean the record does not exist or access is denied.

  • Resolution tips:

    • Double-check the record ID and entity type values.
    • Verify API credentials and network connectivity.
    • Use the "Continue On Fail" option to handle errors gracefully in bulk operations.

Links and References

Discussion