MinIO icon

MinIO

Connect to your MinIO server

Actions11

Overview

This node interacts with an object storage service compatible with the MinIO API. Specifically, the "Object" resource with the "List" operation allows users to list objects stored within a specified bucket. This is useful for scenarios where you want to retrieve and process multiple files or data objects stored in cloud buckets, such as listing all images in a media bucket or enumerating backup files.

Practical examples:

  • Listing all files under a specific folder (prefix) inside a bucket.
  • Recursively listing all objects in a bucket to perform batch processing.
  • Filtering objects by prefix to find files of a certain type or date.

Properties

Name Meaning
Bucket Name The name of the bucket containing the objects. Can be selected from a list of existing buckets or entered manually.
Options Additional options to filter or control the listing:
  Prefix Filter objects that start with this prefix string. Useful for simulating folder-like structures.
  Recursive Boolean flag indicating whether to list objects recursively (true) or only at the top-level directory (false).
  List Options JSON object allowing advanced query parameters, e.g., including versioned objects.

Note: The "Object Name" property exists but is hidden for the "list" operation, as it is not applicable when listing multiple objects.

Output

The node outputs a JSON array of objects representing the listed items in the specified bucket. Each item typically includes metadata such as the object's key (name), size, last modified timestamp, and possibly version information if requested.

If binary data output is supported, it would represent the actual content of the objects, but for the "list" operation, the output is metadata only.

Dependencies

  • Requires connection to a MinIO-compatible object storage service.
  • Needs valid credentials (such as access keys) configured in n8n to authenticate API requests.
  • The node depends on internal methods for listing buckets and objects, which are used to populate dropdowns and perform the listing.

Troubleshooting

  • Common issues:

    • Incorrect bucket name or lack of permissions can cause errors or empty results.
    • Using recursive listing on very large buckets may lead to timeouts or performance issues.
    • Invalid JSON in the "List Options" field can cause parsing errors.

  • Error messages:

    • Authentication failures indicate invalid or missing credentials.
    • "Bucket not found" suggests the specified bucket does not exist or is inaccessible.
    • Malformed query parameters in options will result in request errors.

To resolve these, verify credentials, bucket existence, and ensure correct formatting of input properties.

Links and References

Discussion