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 create a new Vault within a specified project (referred to as a "bucket") and parent vault. A Vault in Basecamp is typically used to securely store files and documents related to a project. This operation is useful when you want to programmatically organize and manage secure storage spaces inside your projects, for example, creating a dedicated vault for confidential contracts or sensitive project documentation.
Practical examples:
- Automatically creating a Vault when a new project is initiated to prepare a secure file repository.
- Organizing files by creating nested vaults under a parent vault for different departments or phases of a project.
- Integrating with other systems to dynamically generate Vaults based on workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the Vault will be created. Used in the API path. |
| Vault ID | The numeric ID of the parent vault under which the new Vault will be created. Used in the API path. |
| Title | The name/title of the new Vault to be created. |
| 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 newly created Vault object returned from the Basecamp API. This includes details such as the Vault's ID, title, creation timestamps, and potentially other metadata provided by the API.
If the "Return Full Response" property is set to true, the output will include the entire HTTP response including status code and headers, not just the Vault data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API authenticated via OAuth2 credentials.
- The node expects the Basecamp account ID to be configured in the credentials to construct the API base URL.
- Network access to Basecamp's API endpoint
https://3.basecampapi.com/is necessary.
Troubleshooting
- Invalid Project or Vault ID: If the provided project or parent vault IDs do not exist or are incorrect, the API will likely return a 404 Not Found error. Verify these IDs before running the node.
- Authentication Errors: Missing or invalid OAuth2 credentials will cause authentication failures. Ensure valid credentials are configured.
- Permission Issues: The authenticated user must have permission to create Vaults in the specified project and parent vault.
- API Rate Limits: Excessive requests may trigger rate limiting; handle retries accordingly.
- Empty or Invalid Title: The Vault title is required; providing an empty string or invalid value may cause the API to reject the request.