Overview
This node is an event trigger designed to activate when a record is deleted in the Axelor platform. It listens for deletion events on a specified Axelor data model and then outputs the details of the deleted record. This is useful for workflows that need to respond immediately to data removals, such as synchronizing deletions with other systems, auditing changes, or cleaning up related data.
Practical examples include:
- Automatically removing corresponding entries in external databases or CRMs when a record is deleted in Axelor.
- Sending notifications or alerts when critical records are deleted.
- Logging deletion events for compliance or audit purposes.
Properties
| Name | Meaning |
|---|---|
| Model Name or ID | Select the Axelor data model to monitor for deletions. Options are loaded dynamically from Axelor metadata. You can also specify a model ID using an expression. |
Output
The node outputs JSON data representing the deleted record received from Axelor. The output contains the full details of the deleted entity as provided by the webhook payload. This allows downstream nodes to access all relevant fields of the deleted record.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication credential for Axelor to establish the webhook and receive deletion events.
- The node depends on Axelor's webhook infrastructure to send POST requests upon record deletions.
- The property options for selecting models are dynamically loaded via an internal method querying Axelor metadata.
Troubleshooting
- Webhook not triggering: Ensure that the webhook URL configured in Axelor matches the path
/axelor/deleteexposed by this node and that Axelor is correctly set to send deletion events. - No data received: Verify that the selected model name or ID is correct and that deletions are occurring on that model.
- Authentication errors: Confirm that the API credentials provided have sufficient permissions to register webhooks and receive data from Axelor.
- Unexpected payload structure: If the output JSON does not match expectations, check Axelor's webhook configuration and payload format, as changes on their side may affect the data structure.
Links and References
- n8n Expressions Documentation
- Axelor official documentation (for webhook setup and model metadata) - consult Axelor's website or support channels.