Actions7
Overview
The node interacts with VolcEngine Cloud Object Storage (TOS/TOD) to perform file and bucket operations. Specifically, the "Delete File" operation deletes a specified file from a TOS bucket. This is useful for managing storage by removing unnecessary or outdated files programmatically.
Practical examples:
- Automatically deleting temporary files after processing.
- Cleaning up user-uploaded files upon account deletion.
- Managing storage costs by removing unused data.
Properties
| Name | Meaning |
|---|---|
| File Path | The path and name of the file in TOS to delete. |
Output
The output JSON contains the result of the delete operation. Typically, this will be an object indicating success or failure of the deletion. There is no binary data output for this operation.
Example output structure (conceptual):
{
"success": true,
"message": "File deleted successfully"
}
Dependencies
- Requires an API key credential for VolcEngine TOS with access permissions.
- Needs configuration of region, endpoint, and bucket information via credentials.
- Uses the official VolcEngine TOS SDK internally to communicate with the cloud service.
Troubleshooting
Common issues:
- Invalid or missing credentials will cause authentication failures.
- Specifying a non-existent file path will likely result in an error indicating the file was not found.
- Insufficient permissions on the bucket or file may cause authorization errors.
Error messages:
"No credentials returned!": Ensure that valid API credentials are configured in n8n.- Errors related to file not found or access denied should be checked against the file path correctness and permission settings.
Resolution tips:
- Verify the file path is correct and the file exists before attempting deletion.
- Confirm that the API key has delete permissions on the target bucket.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.