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 interacts with the Basecamp API to update an existing to-do list within a specified project (referred to as a "bucket" in Basecamp). It allows users to modify the name and description of a to-do list by specifying the project ID and the to-do list ID. This operation is useful for project management workflows where task lists need to be updated dynamically, such as renaming a to-do list to reflect changes in project scope or adding descriptive details to clarify the list's purpose.
Practical examples:
- Renaming a to-do list from "Initial Tasks" to "Phase 1 Tasks" after project planning.
- Adding or updating the description of a to-do list to include deadlines or instructions.
- Automating updates to to-do lists based on external triggers or integrations, e.g., syncing with other task management tools.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the to-do list; used in the API endpoint path. |
| todolistId | The numeric ID of the to-do list to update; used in the API endpoint path. |
| Name | The new name for the to-do list. |
| Todolist Fields | Additional fields for the to-do list; currently supports: |
| - Description | A string describing the to-do list; may contain HTML content. |
| 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 to-do list as returned by the Basecamp API. If the "Return Full Response" option is enabled, the output includes the entire HTTP response object, which contains status code, headers, and body. Otherwise, only the response body (the updated to-do list data) is returned.
The output JSON typically includes fields such as:
id: The ID of the to-do list.name: The updated name of the to-do list.description: The updated description.- Other metadata related to the to-do list as provided by the Basecamp API.
There is no indication that this node outputs binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid credentials including an account identifier and an API access token.
- Network connectivity to Basecamp's API endpoint (
https://3.basecampapi.com/) is necessary.
Troubleshooting
- Invalid Project or To-Do List ID: Errors may occur if the provided project ID or to-do list ID does not exist or the authenticated user lacks permission. Verify IDs and permissions.
- Authentication Errors: Ensure that the OAuth2 credentials are correctly configured and have not expired.
- API Rate Limits: Basecamp API enforces rate limits; hitting these may cause errors. Implement retry logic or reduce request frequency.
- Malformed Input: Providing invalid or empty values for required fields like "Name" may result in validation errors from the API.
- Return Full Response Confusion: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the body may fail. Adjust workflow accordingly.