Actions80
- 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
- Todos Actions
Overview
This node updates an existing Todo item within a specified project bucket in Basecamp. It is useful for managing task details dynamically, such as changing the content, description, assignees, notification settings, and scheduling dates of a Todo. Practical scenarios include updating task assignments after team changes, modifying deadlines, or adding additional context to tasks.
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 notes about the Todo (string). |
| Assignee Ids | JSON array of people IDs to assign the Todo to (e.g., [123, 456]). |
| Completion Subscriber Ids | JSON array of people IDs to notify when the Todo is completed (e.g., [789, 101]). |
| 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 format recommended). |
| Starts On | Date string specifying when the Todo should start (ISO 8601 format recommended). |
Output
The node outputs the updated Todo item data in the json field of the output. This typically includes all properties of the Todo after the update, reflecting the new state as stored in Basecamp. There is no binary data output.
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 accessible and responsive.
Troubleshooting
- Invalid Bucket Id or Todo Id: Errors may occur if the provided IDs do not exist or are incorrect. Verify the IDs before running the node.
- Malformed JSON in Assignee or Subscriber IDs: Ensure that the JSON arrays for
assignee_idsandcompletion_subscriber_idsare valid JSON strings. - Notification Issues: If notifications are not sent, check the
Notifyboolean property and ensure assignees have proper permissions. - Date Format Errors: Use ISO 8601 date formats for
Due OnandStarts Onto avoid parsing errors. - Authentication Failures: Confirm that the OAuth2 credentials are correctly set up and have sufficient permissions.