Mira File Delete

Delete files from Mira App Server library

Mira File Delete

AI-generated

Overview

The "Mira File Delete" node is designed to permanently delete files stored in a specified library on the Mira App Server. It is useful in scenarios where you need to programmatically remove files from your Mira libraries, such as cleaning up outdated or unnecessary documents, automating file lifecycle management, or integrating file deletion into larger workflows.

For example, if you have a workflow that processes files and determines some are no longer needed, this node can be used to delete those files automatically by specifying their library and file IDs.

Properties

Name Meaning
Token Source Choose where to get the access token from: either from stored credentials or directly from input data.
Server URL The URL of the Mira App Server (required if token source is from input).
Access Token The access token for authentication, provided directly or via input data (required if token source is from input).
Library ID The identifier of the library where the target file is stored (required).
File ID The numeric identifier of the file to delete within the specified library (required).
⚠️ Warning: This will permanently delete the file A warning notice indicating that the deletion action is irreversible.

Output

The node outputs an array of JSON objects, each corresponding to an input item processed. Each output JSON contains:

  • operation: Always set to "file_delete" indicating the performed operation.
  • deletedFileId: The ID of the file that was deleted.
  • libraryId: The ID of the library from which the file was deleted.
  • timestamp: ISO string timestamp of when the deletion occurred.

If an error occurs during processing an item and the node is configured to continue on failure, the output JSON for that item will contain an error field with the error message.

The node does not output any binary data.

Dependencies

  • Requires access to a Mira App Server instance reachable via HTTP.
  • Needs a valid access token for authentication, either provided through credentials or input data.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Missing Library ID or File ID: The node throws an error if either the Library ID or File ID is empty or missing. Ensure these fields are correctly set and not blank.
  • Authentication Errors: If the access token is invalid or expired, the HTTP DELETE request will fail. Verify the token's validity and permissions.
  • Server URL Issues: When using token from input, ensure the Server URL is correct and accessible.
  • Network or Server Errors: Any connectivity issues or server-side errors will cause the node to throw errors. Check network connectivity and server health.
  • Continue On Fail Behavior: If enabled, errors for individual items will be captured in the output rather than stopping execution.

Links and References

  • Mira App Server API documentation (for file deletion endpoint): Typically found at [Your Mira App Server URL]/api/docs or contact your Mira administrator.
  • n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/

Discussion