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 allows you to update an existing to-do item within a project (referred to as a "bucket") in Basecamp. It is useful for managing task details dynamically, such as changing the content/title, setting or removing due dates and start dates, assigning people, adding descriptions, and controlling notifications. Practical scenarios include updating task deadlines, reassigning tasks to different team members, or modifying task details based on project progress.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the to-do exists; used to specify the API endpoint path. |
| todoId | The ID of the to-do item to update; used in the API endpoint path. |
| Content | The content or title of the to-do item. |
| Due On | The due date for the to-do; leave empty to remove the due date. |
| Starts On | The start date for the to-do; leave empty to remove the start date. |
| Todo Fields | Additional fields for the to-do, including: |
| - Description | A detailed description of the to-do, which may contain HTML. |
| - Assignee IDs | Comma-separated IDs of people assigned to this to-do. |
| - Completion Subscriber IDs | Comma-separated IDs of people to notify when the to-do is completed. |
| - Notify | Boolean flag indicating whether to notify assignees about being assigned. |
| Return Full Response | Whether to return the full HTTP response (status code, headers, body) instead of only the body. |
Output
The node outputs JSON data representing the updated to-do item as returned by the Basecamp API. This includes all properties of the to-do after the update operation. If the "Return Full Response" option is enabled, the output will include the full HTTP response with status code, headers, and body.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API calls is constructed using the account ID from credentials.
Troubleshooting
- Invalid Project ID or To-Do ID: Errors may occur if the specified project or to-do IDs do not exist or are incorrect. Verify these IDs before running the node.
- Authentication Errors: Ensure that the API key or OAuth2 token is valid and has sufficient permissions to update to-dos.
- Date Format Issues: The "Due On" and "Starts On" fields expect dates in ISO format but only use the date part (YYYY-MM-DD). Providing invalid date formats may cause errors.
- Notification Failures: If "Notify" is set to true but assignee IDs are missing or invalid, notification may fail silently or cause errors.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits; handle such errors by retrying after some delay.