Actions11
Overview
This node checks whether a specified bucket exists in a MinIO or compatible object storage service. It is useful for workflows that need to verify the presence of a bucket before performing operations like uploading files, listing contents, or deleting buckets. For example, before attempting to upload data, you can use this node to confirm the target bucket exists to avoid errors.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket to check for existence. You can select it from a list of existing buckets or specify the bucket name directly as a string. |
Output
The node outputs JSON data indicating the result of the existence check. Typically, this will include a boolean field specifying whether the bucket exists (true or false). There is no binary output associated with this operation.
Dependencies
- Requires connection to a MinIO-compatible object storage service.
- Needs an API authentication token or credentials configured in n8n to access the storage service.
- The node depends on internal methods for listing buckets and checking bucket existence.
Troubleshooting
- Common issues:
- Incorrect or missing credentials may cause authentication failures.
- Specifying a bucket name that does not exist will result in a negative existence check.
- Network connectivity problems can prevent communication with the storage service.
- Error messages:
- Authentication errors indicate invalid or missing API keys; verify credential configuration.
- "Bucket not found" or similar messages mean the bucket does not exist; double-check the bucket name.
- Timeout or connection errors suggest network issues; ensure the service endpoint is reachable.
Links and References
- MinIO Documentation
- S3 Compatible Storage Concepts (for general understanding)