Actions25
- Document Actions
- Function Actions
- Storage Actions
- Users Actions
Overview
This node integrates with Appwrite's Storage service, allowing users to manage files and buckets programmatically within n8n workflows. Specifically, the "Delete File" operation enables the removal of a file from a specified storage bucket in Appwrite. This is useful for automating cleanup tasks, managing storage quotas, or removing outdated or sensitive files as part of a larger workflow.
Practical examples include:
- Automatically deleting user-uploaded files after processing.
- Removing temporary files created during a workflow.
- Cleaning up files based on certain triggers or schedules.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | The unique identifier of the storage bucket where the target file resides. |
| File ID | The unique identifier of the file to be deleted within the specified bucket. |
Output
The output JSON contains a single field success which indicates whether the file deletion was successful (true) or not (false). The node does not output the deleted file data itself.
Example output:
[
{
"success": true
}
]
No binary data is output by this operation.
Dependencies
- Requires an active connection to an Appwrite server.
- Needs credentials including the Appwrite API URL, project ID, and an API key credential with permissions to manage storage.
- The node depends on the official Appwrite SDK (
node-appwrite) to perform API calls.
Troubleshooting
Common issues:
- Invalid or missing Bucket ID or File ID will cause the operation to fail.
- Insufficient permissions in the provided API key may result in authorization errors.
- Network connectivity problems can prevent communication with the Appwrite server.
Error messages:
- Errors related to "file not found" indicate that the specified File ID does not exist in the given bucket.
- Authorization errors suggest checking the API key permissions.
- Timeout or connection errors require verifying network access and Appwrite server availability.
To resolve these issues:
- Double-check the Bucket ID and File ID values.
- Ensure the API key has appropriate storage management rights.
- Confirm the Appwrite endpoint URL and project ID are correct.
- Test connectivity to the Appwrite server outside n8n if needed.