Actions16
- Meta Service Actions
- REST & Advances Service Actions
- Document Service Actions
Document Service → Delete Attachment
AI-generatedOverview
The Delete Attachment operation in the Document Service resource of this n8n node is designed to remove a specific attachment from the Axelor DMS (Document Management System). This is achieved by specifying the ID of the attachment you wish to delete. The node sends a request to the Axelor API to perform the deletion.
Common scenarios:
- Automating the cleanup of obsolete or temporary files in your Axelor DMS.
- Integrating document lifecycle management into business workflows, such as removing attachments after processing.
- Ensuring compliance by programmatically deleting sensitive documents when required.
Practical example:
Suppose you have an automated workflow that processes invoices and, once processed, needs to delete the associated scanned document from Axelor. This node operation can be used to automate that step.
Properties
| Name | Type | Meaning |
|---|---|---|
| Work in progress in this part of node. Please do not break everything. | notice | Informational notice for users about ongoing development in this part of the node. |
| ID | number | The unique identifier of the attachment to delete. You can find this ID in the attachment's URL. |
Output
- The output is a JSON array containing the response from the Axelor API after attempting to delete the specified attachment.
- The structure of the output will reflect the API's response to the deletion request. Typically, this may include status information or confirmation of deletion.
- No binary data is returned by this operation.
Dependencies
- External Service: Requires access to an Axelor instance with the DMS module enabled.
- API Credentials: Needs valid
axelorApicredentials configured in n8n. - Environment/Configuration: Ensure the base URL and authentication details for Axelor are correctly set up in n8n credentials.
Troubleshooting
Common issues:
- Invalid ID: If the provided ID does not correspond to an existing attachment, the API may return an error or empty result.
- Permission Denied: If the API credentials lack permission to delete attachments, the operation will fail.
- Network/API Errors: Connectivity issues or incorrect API endpoint configuration can cause failures.
Error messages and resolutions:
"Attachment not found": Double-check the ID value; ensure it matches an existing attachment."Unauthorized"or"Forbidden": Verify that the API credentials have sufficient permissions."Connection refused"or similar network errors: Check the Axelor server URL and network connectivity.