Actions11
Overview
This node generates presigned URLs for objects stored in a bucket, specifically supporting the "Put" operation. A presigned URL allows users to upload (PUT) an object directly to a storage bucket without requiring direct access credentials. This is useful in scenarios where you want to securely grant temporary upload permissions to clients or external systems.
Practical examples include:
- Allowing users to upload files directly from a web browser to cloud storage without exposing your backend credentials.
- Enabling third-party services to upload data to your storage bucket securely and temporarily.
- Automating file uploads in workflows where the actual file transfer is done outside of n8n but controlled via presigned URLs.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the storage bucket for which to generate the presigned URL. Can be selected from a list of available buckets or specified by ID. |
| Object Name | The key or name of the object within the bucket for which to generate the presigned URL. Can be selected from a list of existing objects or specified by ID. |
Output
The node outputs JSON data containing the generated presigned URL for uploading the specified object to the given bucket. This URL can be used to perform a PUT request to upload the object.
If binary data output is supported, it would typically represent metadata or confirmation related to the presigned URL generation, but based on the provided code and properties, the main output is the presigned URL in JSON format.
Dependencies
- Requires access to a compatible object storage service that supports presigned URLs (e.g., MinIO or S3-compatible storage).
- Needs appropriate API credentials configured in n8n to authenticate and authorize bucket and object access.
- The node depends on internal methods for credential testing and listing buckets/objects, which require proper configuration of the storage connection.
Troubleshooting
- Common issues:
- Invalid bucket or object names may cause errors when generating the presigned URL.
- Missing or incorrect API credentials will prevent successful authentication.
- Network connectivity issues with the storage service can cause timeouts or failures.
- Error messages:
- Authentication errors usually indicate invalid or missing credentials; verify and update the API key or token.
- "Bucket not found" or "Object not found" errors suggest the specified resource does not exist or is inaccessible; check names and permissions.
- Permission denied errors mean the credentials lack sufficient rights; ensure the API key has upload permissions.