Actions44
- User Actions
- Database Actions
- Collection Actions
- Document Actions
- Index Actions
- Function Actions
- Storage Actions
Overview
This node integrates with a cloud storage service to manage files and buckets. Specifically, the "Delete File" operation under the "Storage" resource allows users to delete a file from a specified storage bucket by providing the unique identifiers for both the bucket and the file.
Common scenarios include:
- Cleaning up unused or outdated files in your storage buckets.
- Automating file lifecycle management by deleting files after processing.
- Managing storage costs by removing unnecessary files programmatically.
For example, you might use this node in a workflow that processes uploaded images and deletes the original files once they have been resized and stored elsewhere.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | Unique identifier of the storage bucket where the file resides. Use "unique()" to auto-generate when creating buckets. Required for all file operations. |
| File ID | Unique identifier of the file to be deleted within the specified bucket. |
Output
The output JSON contains a simple success confirmation object:
{
"success": true
}
This indicates that the file deletion was successful.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the cloud storage service.
- The node uses an SDK client internally to communicate with the storage API.
- Proper permissions on the API key are necessary to perform file deletions.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing incorrect or non-existent Bucket ID or File ID will cause errors.
- Insufficient permissions on the API key may result in authorization failures.
- Network connectivity problems can prevent communication with the storage API.
Error messages:
- Errors returned from the API typically include details in the response; these are surfaced as node errors.
- If the node throws an error about missing parameters, ensure both Bucket ID and File ID are provided.
- For permission-related errors, verify that the API key has delete access to the target bucket.
Resolution tips:
- Double-check the Bucket ID and File ID values.
- Confirm API key permissions and validity.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.