Axelor icon

Axelor

Consume Axelor API

Actions16

REST & Advances Service → Advanced Delete

AI-generated

Overview

The REST & Advances Service resource with the Advanced Delete operation (deleteAll) in this n8n custom node is designed to delete multiple records from a specified Axelor domain model in bulk. It sends a POST request to the Axelor API endpoint /ws/rest/{domain}/removeAll with a user-defined JSON body that specifies which records to delete.

Common scenarios:

  • Bulk deletion of records (e.g., removing all outdated sales orders, contacts, or other entities).
  • Automating cleanup tasks in Axelor based on workflow logic.
  • Integrating Axelor data management into broader business automation processes.

Practical example:
You have a list of customer records that need to be deleted from the CRM module in Axelor. By specifying the domain model and providing a filter in the JSON content, you can remove all matching records in one operation.

Properties

Name Type Meaning
Domain Models Resource Locator Selects the Axelor domain model (e.g., com.axelor.apps.sale.db.SaleOrder) to target for deletion.
Content JSON JSON The body of the request; must specify criteria for which records to delete. Should include the domain model.

Output

  • The output is an array of JSON objects returned by the Axelor API after performing the bulk delete operation.
  • The structure of each object depends on the Axelor API's response for the removeAll endpoint, but typically includes status information, number of records deleted, and any error messages if applicable.

Example output:

[
  {
    "status": 0,
    "data": [],
    "message": "3 records deleted"
  }
]

Dependencies

  • External Service: Requires access to an Axelor instance with the REST API enabled.
  • API Key/Credentials: Needs valid Axelor API credentials configured in n8n under the credential type axelorApi.
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common issues:

  • Invalid Domain Model: If the domain model is incorrect or misspelled, the API will return an error indicating the model was not found.
  • Malformed Content JSON: If the JSON body is invalid or missing required fields, the API may respond with a parsing error or indicate missing parameters.
  • Insufficient Permissions: If the API credentials lack permission to delete records, the operation will fail with an authorization error.

Common error messages:

  • "Model not found": Check the spelling and format of the domain model.
  • "Invalid JSON": Ensure the Content JSON is properly formatted.
  • "Permission denied": Verify that the API user has sufficient rights to perform deletions.

Links and References

Discussion