Author: michaelcizmar
Version: 0.0.1
Type: tool
Github: minio-plugin
The MinIO Plugin provides tools for reading and writing files to MinIO object storage. This plugin enables seamless integration between Dify workflows and MinIO-compatible object storage systems, supporting both text and binary content.
The MinioWriter Plugin allows users to write data into MinIO.
- Write text or binary data into MinIO buckets
- Supports base64-encoded binary content
- Configurable content types (MIME types)
- Returns success message with operation details (ETag and size)
| Parameter | Type | Required | Description |
|---|---|---|---|
| object_name | string | Yes | The name of the object/file in the MinIO bucket |
| endpoint | string | Yes | The endpoint URL of the MinIO server (e.g., http://localhost:9000) |
| access_key | string | Yes | The access key for MinIO authentication |
| secret_key | string | Yes | The secret key for MinIO authentication |
| bucket_name | string | Yes | The name of the MinIO bucket to write to |
| content | string | Yes | The content to write to the object (text or base64-encoded binary) |
| content_type | string | No | MIME type of the content (optional, defaults to application/octet-stream) |
| is_binary | boolean | No | Whether the content is base64-encoded binary data (defaults to false) |
The MinioReader Plugin allows users to read data from MinIO.
- Read text or binary files from MinIO buckets
- Automatically detects content type (text vs binary)
- Returns text content as plain text
- Returns binary content as blob with metadata (filename, MIME type)
| Parameter | Type | Required | Description |
|---|---|---|---|
| object_name | string | Yes | The name of the object/file in the MinIO bucket |
| endpoint | string | Yes | The endpoint URL of the MinIO server (e.g., http://localhost:9000) |
| access_key | string | Yes | The access key for MinIO authentication |
| secret_key | string | Yes | The secret key for MinIO authentication |
| bucket_name | string | Yes | The name of the MinIO bucket to read from |
- Ensure you have permission to access the target MinIO server
- Sensitive information such as access keys and secret keys should be kept secure
- Credentials are passed as workflow parameters and are not stored persistently by the plugin
- Use HTTPS endpoints for production environments
- Follow the principle of least privilege, granting only necessary execution permissions
- Ensure your MinIO server is properly secured and accessible only to authorized users