Axelor icon

Axelor

Consume Axelor API

Actions16

REST & Advances Service → Delete a Record

AI-generated

Overview

The Delete a Record operation for the "REST & Advances Service" resource in this n8n node allows you to delete a specific record from an Axelor domain model by its ID. This is useful when you need to automate the removal of records (such as orders, customers, or other entities) from your Axelor ERP system directly from n8n workflows.

Common scenarios:

  • Automatically deleting obsolete or test data after processing.
  • Removing records based on business logic or workflow triggers.
  • Integrating with other systems that require cleanup of Axelor data.

Example:
You have a workflow that processes sales orders and, under certain conditions, needs to delete a specific order from Axelor by its unique ID.

Properties

Name Type Meaning
Domain Models Resource Locator Selects the domain model (e.g., com.axelor.apps.sale.db.SaleOrder) to operate on.
ID Number The unique identifier of the specific record you want to delete within the chosen domain.

Output

  • The output will be a JSON array containing the response from the Axelor API after attempting to delete the specified record.
  • Typically, the response may include a status message or confirmation of deletion, but the exact structure depends on the Axelor API's implementation.
  • No binary data is returned by this operation.

Example output:

[
  {
    "status": "success",
    "message": "Record deleted successfully"
  }
]

Note: Actual output may vary depending on the Axelor API.

Dependencies

  • External Service: Requires access to an Axelor instance with REST API enabled.
  • Credentials: Needs an n8n credential named axelorApi configured with appropriate permissions to perform deletions.
  • Environment: Ensure network connectivity between n8n and the Axelor server.

Troubleshooting

Common issues:

  • Invalid Domain Model: If the selected domain model does not exist, the API may return a "404 Not Found" or similar error.
  • Missing or Invalid ID: If the ID is missing or does not correspond to an existing record, deletion will fail.
  • Insufficient Permissions: If the provided credentials lack delete permissions, the API may return a "403 Forbidden" or "401 Unauthorized" error.
  • API Connection Issues: Network or authentication problems can result in connection errors.

How to resolve:

  • Double-check the domain model and ID values.
  • Ensure the Axelor user has permission to delete records in the specified domain.
  • Verify the Axelor API URL and credentials in n8n settings.

Links and References

Discussion