MinIO icon

MinIO

Connect to your MinIO server

Actions11

Overview

This node interacts with objects stored in buckets, specifically supporting the "Get" operation on an object resource. It allows users to retrieve an object (file or data blob) from a specified bucket by its name. This is useful in scenarios where you need to fetch files or data stored remotely for further processing, such as downloading images, documents, or any binary data from cloud storage.

Practical examples include:

  • Downloading a user-uploaded file from a cloud bucket to process it within an automation workflow.
  • Retrieving configuration files or assets stored remotely to use them dynamically in workflows.
  • Accessing backups or logs stored as objects in buckets for analysis.

Properties

Name Meaning
Bucket Name The name of the bucket containing the object. Can be selected from a list of available buckets or provided directly as a string ID.
Object Name The name (key) of the object inside the bucket. Can be selected from a list of objects in the chosen bucket or provided directly as a string ID.
Field Name The name of the binary field in which to store the retrieved object data. Defaults to "data".

Output

The node outputs the retrieved object data in the json output field under the specified binary field name (default "data"). This binary field contains the raw content of the object fetched from the bucket, allowing subsequent nodes to access or manipulate the file/data.

If the object is a file or binary data, it will be accessible as binary data attached to the item, enabling workflows to handle downloads, transformations, or uploads elsewhere.

Dependencies

  • Requires access to a compatible bucket storage service (e.g., MinIO or S3-compatible storage).
  • Needs proper authentication credentials configured in n8n to connect and authorize requests to the bucket service.
  • The node depends on internal methods for listing buckets and objects to support selection from lists.

Troubleshooting

  • Common issues:

    • Incorrect bucket or object names may cause the node to fail to find the requested object.
    • Missing or invalid authentication credentials will prevent connection to the storage service.
    • Network connectivity problems can cause timeouts or failures when accessing the bucket.

  • Error messages and resolutions:

    • "Object not found" — Verify that the bucket and object names are correct and exist.
    • "Authentication failed" — Check that the API key or credentials are correctly set up and have sufficient permissions.
    • "Network error" — Ensure network access to the storage endpoint is available and not blocked by firewalls.

Links and References

Discussion