Actions11
Overview
This node operation generates a presigned URL for an object stored in a bucket. A presigned URL allows temporary, secure access to a specific object without requiring direct authentication. This is useful for sharing private files with external users or services for a limited time.
Common scenarios include:
- Providing temporary download links to users.
- Allowing uploads to a storage bucket without exposing credentials.
- Integrating with external systems that require time-limited access to objects.
For example, you might generate a presigned URL valid for one hour to let a client download a report stored in your bucket.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket containing the object. Can be selected from a list of buckets or entered manually. |
| Object Name | The key (name) of the object within the bucket. Can be selected from a list of objects or entered manually. |
| Options | Additional options for generating the presigned URL: |
| - Expiration | Time in seconds before the presigned URL expires (default is 604800 seconds = 7 days). |
| - Response Headers | Custom HTTP response headers to override when accessing the URL (e.g., content-disposition). Each header requires a name and value. |
| - Request Date | The date/time at which the URL will be issued. Useful for backdating or future-dating the URL issuance. |
Output
The node outputs JSON data containing the generated presigned URL. The exact structure typically includes a field with the URL string that can be used directly to access the object.
If binary data output is supported, it would represent the actual file content fetched via the presigned URL, but based on the provided information, the main output is the URL itself.
Dependencies
- Requires connection to an object storage service compatible with presigned URLs (e.g., S3-compatible storage).
- Needs appropriate API credentials configured in n8n to authenticate and authorize access to the bucket and object.
- No additional environment variables are explicitly required beyond standard credential setup.
Troubleshooting
- Invalid Bucket or Object Name: If the bucket or object does not exist or is misspelled, the node will fail to generate a URL. Verify names carefully.
- Expired Credentials: Authentication failures may occur if the API key or token has expired or lacks permissions.
- Incorrect Expiration Value: Setting expiration too low or too high might cause unexpected behavior; use reasonable values.
- Response Header Misconfiguration: Invalid or unsupported headers in the options may cause errors or ignored overrides.
- Date Issues: Providing an invalid request date could lead to signature validation errors.
To resolve these issues:
- Double-check bucket and object names.
- Ensure credentials have sufficient permissions.
- Use default expiration unless a specific need exists.
- Validate custom headers for correctness.
- Use proper ISO date formats for request date.
Links and References
- AWS S3 Presigned URLs Documentation (conceptual reference)
- MinIO Presigned URL Guide (if using MinIO backend)
- n8n documentation on Resource Locators for understanding bucket/object selection modes