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 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.
Common scenarios where this node is beneficial include:
- Updating task details after receiving new information or changes in project scope.
- Reassigning tasks to different team members.
- Adjusting deadlines or start dates for better project management.
- Adding subscribers who should be notified upon task completion.
For example, a project manager can use this node to update the content and due date of a Todo when priorities shift, ensuring all stakeholders are informed and aligned.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the Todo to update. |
| Todo Id | ID of the specific Todo item to update. |
| Content | The main text or title describing what the Todo is for. |
| Description | Additional detailed information about the Todo. |
| Assignee Ids | JSON array of user IDs to assign the Todo to. |
| Completion Subscriber Ids | JSON array of user IDs to notify when the Todo is completed. |
| Notify | Boolean flag indicating whether to notify assignees about their assignment (true/false). |
| Due On | Date string specifying when the Todo should be completed. |
| Starts On | Date string specifying when the Todo should start. |
Output
The node outputs JSON data representing the updated Todo item as returned by the Basecamp API. This typically includes fields such as the Todo's ID, content, description, assignees, completion status, and relevant timestamps.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- The node uses the Basecamp API endpoint scoped to the user's Basecamp account ID.
- Proper permissions on the Basecamp project and Todos are necessary to perform updates.
Troubleshooting
- Invalid Bucket Id or Todo Id: If the provided IDs do not exist or the user lacks access, the API will return an error. Verify that the IDs are correct and accessible.
- Malformed JSON in Assignee or Subscriber IDs: The
assignee_idsandcompletion_subscriber_idsproperties expect valid JSON arrays. Invalid JSON will cause parsing errors. Ensure these inputs are correctly formatted. - Notification Issues: If
Notifyis set to false, assignees will not receive notifications. Confirm this setting if notifications are expected but not received. - Date Format Errors: The
Due OnandStarts Onfields require valid date strings. Incorrect formats may lead to API rejection. Use ISO 8601 date format (e.g., "2024-12-31"). - API Authentication Failures: Ensure the API key or OAuth token is valid and has not expired.