Actions7
Overview
This node enables interaction with VolcEngine Cloud Object Storage (TOS/TOD). Specifically, the Download File operation allows users to download a file stored in TOS by specifying its path. It can return the file content as binary data or just metadata about the file.
Common scenarios where this node is useful include:
- Retrieving files stored in VolcEngine TOS for further processing or analysis within an n8n workflow.
- Downloading images, documents, or other assets from cloud storage to use in automation tasks.
- Archiving or backing up files by fetching them from TOS and saving elsewhere.
For example, you might use this node to download a report PDF generated and stored in TOS, then send it via email or upload it to another service.
Properties
| Name | Meaning |
|---|---|
| File Path | The full path and filename of the file in VolcEngine TOS to download. |
| Return Binary Data | Whether to return the actual file content as binary data (true) or only metadata (false). |
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains:
json: An object with metadata about the downloaded file (e.g., file info, URLs).binary(optional): If "Return Binary Data" is enabled, this field contains the raw binary content of the downloaded file under a binary property.
If binary data is returned, it can be used downstream in workflows that require file contents, such as uploading to another service or processing the file.
Dependencies
- Requires valid credentials for VolcEngine TOS API access, including access key, secret key, region, endpoint, and bucket name.
- Uses the official VolcEngine TOS SDK for JavaScript to interact with the storage service.
- Must configure the node with appropriate API credentials before execution.
Troubleshooting
No credentials returned!
This error occurs if the node cannot find or access the required API credentials. Ensure that the credentials are properly set up and linked to the node.File not found or access denied errors
Verify that the specified file path exists in the configured bucket and that the credentials have permission to read the file.Binary data missing despite enabling "Return Binary Data"
Confirm that the file actually contains data and that the node has sufficient permissions to download it.Network or endpoint errors
Check network connectivity and verify that the endpoint URL and region are correctly configured.