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 integrates with the Basecamp API to update an existing Vault within a specified project (bucket). It allows users to modify the title of a Vault by specifying the project ID and vault ID. This operation is useful for managing and organizing secure storage areas (Vaults) in Basecamp projects, such as updating the name to reflect changes in content or purpose.
Practical examples include:
- Renaming a Vault after restructuring project files.
- Correcting typos or updating Vault titles to match new naming conventions.
- Automating Vault updates as part of a larger workflow that manages project resources.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the Vault exists; used in the API endpoint path. |
| vaultId | The numeric ID of the Vault to update; used in the API endpoint path. |
| Title | The new name/title for the Vault. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the updated Vault resource returned from the Basecamp API. If "Return Full Response" is enabled, the output includes the full HTTP response object containing status code, headers, and body; otherwise, only the response body (the updated Vault details) is returned.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node uses the Basecamp API base URL constructed dynamically using the authenticated account ID.
- Proper permissions on the Basecamp account are necessary to update Vaults within projects.
Troubleshooting
Common Issues:
- Invalid or missing Project ID or Vault ID will cause the API call to fail.
- Insufficient permissions or expired authentication tokens can result in authorization errors.
- Providing an empty or invalid title may lead to validation errors from the API.
Error Messages:
- 404 Not Found: The specified project or vault does not exist. Verify IDs.
- 401 Unauthorized: Authentication failed. Check API credentials and re-authenticate if needed.
- 400 Bad Request: Invalid input data, such as missing required fields or invalid title format.
Resolutions:
- Double-check the Project ID and Vault ID values.
- Ensure the API credentials are valid and have appropriate scopes.
- Validate the title string before sending the request.