Actions80
- 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
- Todos Actions
Overview
The "Update Upload" operation in the Uploads resource allows users to modify metadata of an existing file upload within a specified storage bucket. This node is useful when you want to update descriptive information or rename an uploaded file without re-uploading it. For example, you might want to add or change the description of a file to provide more context or update the base name of the file to better reflect its content.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket where the upload resides. |
| Upload Id | The 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 after the changes have been applied. This typically includes the updated fields such as the new description and base name, along with other metadata related to the upload. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authentication with the external service managing uploads.
- The node sends HTTP requests to the service's API endpoint, which must be accessible from the n8n environment.
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
- Invalid Bucket Id or Upload Id: If either ID does not exist or is incorrect, 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 provided API key lacks permissions to update uploads. Ensure the API key has appropriate scopes.
- Malformed Description: Since the description supports HTML, invalid or unsafe HTML might cause issues on the server side. Validate or sanitize input if necessary.
- Empty Base Name: Providing an empty string for the base name might result in an error or undesired behavior depending on the API. Confirm whether the field can be left blank or must be omitted if unchanged.
Links and References
- Refer to the official API documentation of the upload management service for detailed information on the update upload endpoint and supported fields.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes if custom modifications are needed.