Actions11
Overview
This node operation uploads (puts) an object into a specified bucket in a storage service compatible with the MinIO API. It is useful for scenarios where you want to programmatically store files or data blobs into cloud or on-premise object storage. For example, you might use this node to save user-uploaded images, backup logs, or export reports as files into a bucket.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket where the object will be stored. Can be selected from a list or entered manually. |
| Object Name | The key or name of the object inside the bucket. Can be selected from a list or entered manually. |
| Field Name | The name of the binary field from the input data that contains the content to upload. Default is "data". |
| Options | Additional optional settings: - Object Name: alternative way to specify the object name. - Metadata: JSON object containing metadata to associate with the uploaded object. |
Output
The node outputs JSON data representing the result of the put operation. This typically includes confirmation details such as the bucket and object names, and possibly metadata or status information returned by the storage service. If the node supports binary data output, it would relate to the uploaded object's content or related binary responses, but here the focus is on uploading binary data from input rather than outputting binary data.
Dependencies
- Requires access to a MinIO-compatible object storage service.
- Needs appropriate credentials (such as an API key or token) configured in n8n to authenticate requests.
- The node depends on internal methods for listing buckets and objects to support resource locators.
- No external libraries beyond those bundled with the node are explicitly required.
Troubleshooting
- Common issues:
- Incorrect bucket or object names leading to "not found" errors.
- Missing or incorrect binary data in the specified field causing upload failures.
- Authentication errors if credentials are invalid or missing.
- Error messages:
- Errors indicating inability to find the bucket or object usually mean the names are wrong or the bucket does not exist.
- Permission denied or authentication failed errors suggest checking the API key or credential setup.
- Upload failures due to empty or missing binary data require verifying the input data and the field name property.
Links and References
- MinIO Documentation
- S3 Compatible Storage Concepts (MinIO is S3 compatible)
- n8n documentation on working with binary data