Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node operation updates an existing upload in a specified bucket. It allows users to modify metadata related to the upload, such as its description and base file name (without extension). This is useful when you want to correct or enhance information about a file already stored, for example updating the description to provide more context or renaming the file for clarity without re-uploading it.
Practical examples:
- Updating the description of an uploaded document to include additional details or formatting in HTML.
- Changing the base name of a file after upload to better reflect its content or purpose.
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 updated fields such as the new description, base name, and other metadata reflecting the current state of the upload after modification.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the external service managing uploads.
- The node uses a base URL constructed dynamically from credentials (e.g., a basecampId), so proper credential configuration is necessary.
- The request headers specify JSON content type and accept JSON responses.
Troubleshooting
- Missing or invalid Bucket Id or Upload Id: The operation requires both identifiers; ensure they are provided and valid numbers.
- Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Invalid description format: The description should be valid HTML if used; malformed HTML might cause unexpected results.
- Empty or invalid base name: Ensure the base name does not contain forbidden characters and is appropriate for a file name.
- API errors: Check the response message for details; common issues include resource not found (wrong IDs) or permission denied.
Links and References
- Refer to the external API documentation for "Uploads" management to understand all possible fields and constraints.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes for similar operations.