Actions11
Overview
This node operation lists buckets in a MinIO or compatible object storage service. It is useful when you want to retrieve and display all available buckets or verify the existence of specific buckets within your storage environment. Typical use cases include managing storage resources, automating backup workflows, or integrating bucket data into larger automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket to operate on. Can be selected from a list of existing buckets or specified by ID. |
Output
The output contains a JSON array representing the list of buckets retrieved from the storage service. Each item typically includes metadata about a bucket such as its name and creation date. This allows subsequent nodes to process or filter buckets based on their attributes.
If the node supports binary data output (not explicitly shown here), it would represent any associated binary content related to the buckets, but this is not indicated in the provided code snippet.
Dependencies
- Requires connection to a MinIO-compatible object storage service.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the storage service.
- The node depends on internal methods for executing operations and listing/searching buckets, which are part of the bundled source code.
Troubleshooting
- Common issues:
- Authentication failures due to incorrect or missing API credentials.
- Network connectivity problems preventing access to the storage endpoint.
- Specifying a bucket name that does not exist or is inaccessible.
- Error messages:
- Errors related to authorization usually indicate invalid or expired credentials; reconfigure the API key or token.
- Connection timeout errors suggest network issues or incorrect service URLs.
- "Bucket not found" errors mean the specified bucket name is incorrect or the user lacks permissions.