Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node operation retrieves a specific upload from a designated storage bucket. It is useful when you need to access or process a particular file that has been previously uploaded and stored in a bucket. For example, you might use this node to fetch an image or document by its unique upload ID within a given bucket for further processing, analysis, or transfer.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the storage bucket where the upload resides. |
| Upload Id | The numeric identifier of the specific upload (file) to retrieve. |
Output
The output contains a JSON object representing the details and metadata of the requested upload. This typically includes information such as the file name, size, type, URL, and other relevant attributes describing the upload. If the node supports binary data output, it would represent the actual file content; however, based on the provided code snippet, only JSON metadata output is evident.
Dependencies
- Requires an API key credential for authentication with the external service managing the buckets and uploads.
- The node depends on a REST API endpoint structured around bucket and upload IDs to fetch the upload data.
- Proper configuration of the API base URL and authentication credentials is necessary within n8n.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id or Upload Id will result in errors or empty responses.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity issues preventing access to the external API.
Error Messages:
- "Upload not found" or similar indicates the specified upload ID does not exist in the given bucket.
- "Unauthorized" or "Authentication failed" suggests problems with the API key or credentials.
Resolutions:
- Verify that both Bucket Id and Upload Id are correct and correspond to existing resources.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network settings and API endpoint accessibility.
Links and References
- Refer to the external service’s API documentation for detailed information about bucket and upload management endpoints.
- Consult n8n documentation on how to configure API key credentials and handle HTTP request nodes.