Actions119
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node operation updates an existing upload within a specified project in Basecamp. It allows users to modify metadata of an upload such as its description or base filename without re-uploading the file itself. This is useful for correcting or enhancing information about files already stored in a project, improving organization and clarity.
Common scenarios:
- Updating the description of a document or image after initial upload to add more context or formatting (including HTML).
- Renaming the base filename of an upload to better reflect its content or purpose.
- Adjusting upload details programmatically as part of a workflow that manages project assets.
Practical example:
A marketing team automates updating descriptions of uploaded campaign images with formatted text describing usage rights or version notes, ensuring all collaborators see consistent and detailed information.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the upload exists; used in the API path. |
| Upload ID | The numeric ID of the upload to update; used in the API path. |
| Upload Fields | Fields to update on the upload. Options include: - Description: New description text (may contain HTML). - Base Filename: New base filename without extension. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) instead of just the response body. |
Output
The output JSON contains the updated upload object returned from the Basecamp API. This typically includes fields such as:
id: The upload's unique identifier.description: The updated description of the upload.base_name: The updated base filename.- Other metadata related to the upload like URLs, timestamps, and associated project info.
If "Return Full Response" is enabled, the output will include the entire HTTP response structure including status code and headers alongside the body.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and upload IDs corresponding to existing resources in Basecamp.
- Proper permissions are needed to update uploads within the specified project.
Troubleshooting
- Invalid Project or Upload ID: Errors may occur if the provided IDs do not exist or the authenticated user lacks access. Verify IDs and permissions.
- Insufficient Permissions: The API may reject updates if the OAuth token does not have write access to the project or upload.
- Malformed Description or Filename: Ensure that the description string is properly formatted (HTML allowed) and the base filename does not include extensions or invalid characters.
- API Rate Limits or Network Issues: Temporary failures might happen due to rate limiting or connectivity problems; retry after some time.
- Return Full Response Misuse: If enabled, downstream nodes must handle the full HTTP response object; otherwise, unexpected data structures may cause errors.