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
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 (filename 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 copyright or usage details.
- Renaming a document upload to follow a new naming convention without re-uploading the file.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the storage bucket containing the upload to update. |
| Upload Id | Numeric identifier of the specific upload to be updated within the bucket. |
| Description | Optional HTML-formatted text providing additional information about the upload. |
| Base Name | New filename (without extension) to rename the upload. |
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, base name, and other metadata related to the upload. The output does not include binary data; it focuses on metadata confirmation after the update.
Dependencies
- Requires an API key credential for authenticating with 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.
- No additional external libraries beyond those bundled are required.
Troubleshooting
- Invalid Bucket Id or Upload Id: If these IDs do not correspond to existing resources, the API will likely return an error. Verify the IDs before running the node.
- Authentication errors: Ensure the API key or OAuth token is valid and has sufficient permissions to update uploads.
- Malformed Description: Since the description supports HTML, invalid markup might cause issues depending on the API's validation rules.
- Empty Base Name: Providing an empty string for the base name may either clear the filename or cause an error; check API documentation for allowed values.
Common error messages might include "Resource not found" for invalid IDs or "Unauthorized" for authentication failures. Resolving these involves verifying input parameters and credentials.
Links and References
- Refer to the external API documentation for detailed information on upload resource management and field constraints.
- Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.