Actions11
Overview
This node interacts with an object storage service compatible with the MinIO API. Specifically, the "Object" resource with the "Stat" operation retrieves metadata about a specific object stored in a bucket. This is useful when you need to check details such as size, last modified date, or other metadata of an object without downloading it.
Common scenarios include:
- Verifying if an object exists and inspecting its properties before processing.
- Checking object metadata for logging or auditing purposes.
- Conditional workflows based on object attributes like size or modification date.
Example: Before triggering a file processing workflow, use this node to confirm the file's presence and retrieve its metadata.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket containing the object. Can be selected from a list of buckets or specified by ID. |
| Object Name | The name (key) of the object within the bucket. Can be selected from a list of objects or specified by ID. |
Output
The node outputs JSON data representing the metadata of the specified object. This typically includes fields such as:
- Object size
- Last modified timestamp
- ETag or checksum
- Content type
- Any custom metadata associated with the object
No binary data output is produced by this operation; it strictly returns metadata information.
Dependencies
- Requires connection to a MinIO-compatible object storage service.
- Needs appropriate credentials (e.g., access key and secret key) configured in n8n to authenticate requests.
- The node depends on internal methods for listing buckets and objects to support the resource locator input modes.
Troubleshooting
- Object Not Found: If the specified object does not exist, the node may throw an error indicating the object was not found. Verify the bucket and object names are correct.
- Authentication Errors: Ensure that the API credentials are valid and have sufficient permissions to access the bucket and object.
- Network Issues: Connectivity problems to the MinIO server can cause timeouts or failures. Check network settings and endpoint URLs.
- Incorrect Resource Locator Mode: When using the "From List" mode, ensure that the list methods are correctly returning available buckets and objects; otherwise, selection might fail.