Actions25
Overview
This node integrates with the EspoCRM API to perform various operations on CRM entities such as accounts, contacts, leads, and custom entities. Specifically for the Account - Delete operation, it deletes an account record identified by its Account ID from the EspoCRM system.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or invalid account records.
- Integrating with other systems to synchronize deletions in EspoCRM.
- Building workflows that manage account lifecycle events, including removal.
For example, a workflow could trigger when an account is marked inactive in another system and use this node to delete the corresponding account in EspoCRM automatically.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account to delete. This is required to specify which account record should be removed from EspoCRM. |
Output
The output JSON array contains objects representing the result of each deletion attempt. For the Account Delete operation, each object includes:
success: A boolean indicating whether the deletion was successful (true).id: The Account ID that was deleted.entityType: The type of entity deleted, here always"account".
Example output:
[
{
"success": true,
"id": "12345",
"entityType": "account"
}
]
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to an EspoCRM instance via an API key credential configured in n8n.
- The node uses the EspoCRM REST API endpoints to perform CRUD operations.
- Proper permissions in EspoCRM are necessary to delete account records.
Troubleshooting
Common issues:
- Invalid or missing Account ID will cause the operation to fail.
- Insufficient permissions in EspoCRM to delete accounts.
- Network or authentication errors connecting to the EspoCRM API.
Error messages:
"The operation "delete" is not supported for resource type "account": This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API errors returned from EspoCRM (e.g., 404 Not Found if the Account ID does not exist) will be surfaced as error messages.
Resolution tips:
- Verify the Account ID is correct and exists in EspoCRM.
- Check API credentials and permissions.
- Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.
Links and References
- EspoCRM API Documentation
- n8n Documentation on Expressions (useful for dynamic parameter values)