Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation updates an existing file upload within a specified storage bucket. It allows users to modify metadata such as the description and the base name (file name without extension) of the uploaded file. This is useful in scenarios where you need to correct or enhance information about a file after it has been initially uploaded, for example updating the description to provide more context or renaming the file for better organization.
Practical examples:
- Updating the description of an image upload to include details about its content or usage rights.
- Renaming a document upload to follow a new naming convention without changing the file extension.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the upload resides. |
| Upload Id | Numeric identifier of the specific upload to update. |
| Description | Optional HTML-formatted text providing information about the upload. |
| Base Name | New file name for the upload without the file extension. |
Output
The node outputs JSON data representing the updated upload object returned by the API. This typically includes the updated fields such as the new description and base name, along with other metadata related to the upload. The output does not indicate binary data handling for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing uploads.
- The node uses a base URL constructed dynamically from credentials, indicating that the user must configure appropriate authentication and connection details in n8n.
Troubleshooting
- Invalid Bucket Id or Upload Id: If these identifiers are incorrect or do not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Insufficient Permissions: Errors related to authorization may occur if the API key lacks permissions to update uploads. Ensure the API key has the necessary scopes.
- Malformed Description: Since the description supports HTML, invalid or unsafe HTML might cause issues. Validate or sanitize input if errors arise.
- Empty Required Fields: Bucket Id and Upload Id are required; missing these will cause the node to fail.
Links and References
- Refer to the external service’s API documentation for "uploads" management to understand all possible fields and constraints.
- n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.