Actions11
Overview
This node checks whether a specified bucket exists in a MinIO storage service. It is useful for workflows that need to verify the presence of a bucket before performing further operations such as 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 it by ID (string). |
Output
The node outputs JSON data indicating whether the specified bucket exists. Typically, this will be a boolean flag or an object containing the existence status. There is no indication that binary data is output by this operation.
Dependencies
- Requires connection to a MinIO-compatible storage service.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the MinIO instance.
- The node depends on internal methods for credential testing and listing buckets to support the "Bucket Name" property modes.
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 with the MinIO server can cause timeouts or errors.
- Error messages:
- Authentication errors typically indicate invalid or missing API keys.
- Errors about bucket not found mean the bucket does not exist or the user lacks permission.
- Resolutions:
- Verify and update the API credentials.
- Confirm the bucket name is correct and accessible.
- Check network connectivity and endpoint configuration.