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 Download File operation allows users to download a file stored in a specified bucket by providing the unique identifiers for both the bucket and the file.
Common scenarios where this node is beneficial include:
- Automating retrieval of files from cloud storage for further processing or backup.
- Integrating file downloads into workflows that require access to stored documents, images, or other media.
- Building pipelines that fetch files on-demand based on triggers or schedules.
For example, you could use this node to automatically download user-uploaded images from a storage bucket and then process them in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | Unique identifier of the storage bucket containing the file. Use "unique()" to auto-generate when creating a bucket. Required for all file operations. |
| File ID | Unique identifier of the file to be downloaded within the specified bucket. |
Output
The output contains binary data representing the downloaded file:
- The
jsonfield includes metadata about the operation success and a message indicating the file is prepared for download. - The
binaryfield contains the actual file data under a property nameddata. This binary data can be used in subsequent nodes for saving, processing, or transferring the file.
Example output structure (simplified):
[
{
"json": {
"success": true,
"message": "File <fileId> prepared for download."
},
"binary": {
"data": {
"data": "<binary file content>",
"mimeType": "<file mime type>"
}
}
}
]
Dependencies
- Requires an API key credential for authenticating with the cloud storage service.
- The node uses the service's SDK client internally to perform operations.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing incorrect or non-existent Bucket ID or File ID will result in errors indicating the resource was not found.
- Missing or invalid API credentials will cause authentication failures.
- Attempting to download very large files may lead to memory or timeout issues depending on the execution environment.
Error messages:
- Errors returned from the service typically include HTTP response details. These are surfaced in the error object under a response property.
- If the node fails due to network or permission issues, ensure the API key has sufficient rights to access the specified bucket and file.
- To handle errors gracefully, enable the "Continue On Fail" option in the node settings to capture error details without stopping the entire workflow.
Links and References
- Appwrite Storage API Documentation — Official documentation for managing storage buckets and files.
- n8n Documentation — General guidance on using n8n nodes and handling binary data.