Actions11
Overview
This node interacts with objects stored in buckets, specifically supporting the "Get" operation on an object resource. It allows users to retrieve the content of a specified object (file) from a chosen bucket. This is useful in scenarios where you need to fetch files or data blobs stored remotely for further processing, analysis, or transfer within an automation workflow.
Practical examples include:
- Downloading a configuration file stored in a cloud bucket to update system settings.
- Retrieving images or documents stored remotely to process or send them via email.
- Accessing backup files for validation or restoration purposes.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket containing the object. Can be selected from a list of available buckets or entered manually as an ID. |
| Object Name | The name (key) of the object inside the bucket. Can be selected from a list of objects or entered manually as an ID. |
| Field Name | The name of the binary field where the retrieved object data will be stored. Defaults to "data". |
| Options | Additional JSON options to customize how the object is retrieved. This can include parameters like versioning, encryption context, or other service-specific get options. |
Output
The node outputs the retrieved object data in the json output field. The actual content of the object is stored in a binary field named according to the "Field Name" property (default is "data"). This binary data represents the raw content of the object fetched from the bucket.
Thus, downstream nodes can access this binary data for further processing, such as saving to disk, sending over HTTP, or parsing.
Dependencies
- Requires connection to a compatible object storage service that supports bucket and object operations.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the storage 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 leading to "object not found" errors.
- Insufficient permissions or invalid credentials causing authorization failures.
- Network connectivity problems preventing access to the storage service.
Error messages and resolutions:
- "Object not found": Verify the bucket and object names are correct and exist.
- "Access denied" or "Unauthorized": Check that the API key or authentication token has sufficient permissions.
- Timeout or network errors: Ensure the service endpoint is reachable and there are no firewall restrictions.
Links and References
- Refer to your object storage provider's API documentation for details on supported get options and authentication.
- n8n documentation on working with binary data and resource locators for more information on configuring these properties.