Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation updates an existing Todo item within a specified project bucket in Basecamp. It allows users to modify various attributes of a Todo such as its content, description, assignees, notification settings, and scheduling dates. This is useful for managing task details dynamically, ensuring that Todos reflect the latest requirements or changes in project scope.
Practical examples include:
- Changing the content or description of a task when project priorities shift.
- Reassigning tasks to different team members.
- Adjusting due dates or start dates based on updated timelines.
- Controlling notifications to keep relevant people informed about assignments.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket where the Todo resides (number). |
| Todo Id | ID of the specific Todo item to update (number). |
| Content | The main text or title describing what the Todo is for (string). |
| Description | Additional information or details about the Todo (string). |
| Assignee Ids | JSON array of person IDs to assign the Todo to (array of numbers or null). |
| Completion Subscriber Ids | JSON array of person IDs to notify upon completion of the Todo (array of numbers or null). |
| Notify | Boolean flag indicating whether to notify assignees about being assigned (true/false). |
| Due On | Date string specifying when the Todo should be completed (ISO 8601 date format). |
| Starts On | Date string specifying when the Todo should start (ISO 8601 date format). |
Output
The node outputs JSON data representing the updated Todo item as returned by the Basecamp API. This typically includes all current properties of the Todo after the update, such as its ID, content, description, assignees, notification settings, and scheduling dates.
If the node supports binary data output, it is not indicated here; the focus is on JSON response data reflecting the updated Todo state.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- Needs the Basecamp account ID to construct the API base URL.
- Relies on the Basecamp API service being available and accessible.
Troubleshooting
- Invalid Bucket Id or Todo Id: Errors may occur if the provided IDs do not exist or are incorrect. Verify these IDs in your Basecamp project.
- Malformed JSON in Assignee or Subscriber IDs: Ensure the JSON arrays for
assignee_idsandcompletion_subscriber_idsare valid JSON strings. - Permission Denied: If the API token lacks permissions to update Todos, the request will fail. Confirm the OAuth2 token has appropriate scopes.
- Date Format Issues: Dates must be in a valid ISO 8601 format. Invalid date strings can cause errors.
- Notification Flag Misuse: Setting
notifyincorrectly might result in unexpected notification behavior; use true/false appropriately.