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 marks a specific todo item as completed within a project bucket in Basecamp. It is useful for automating task management workflows, such as updating the status of tasks when certain conditions are met or integrating with other systems to reflect progress automatically.
Practical examples include:
- Automatically completing todos when a related issue is resolved in an external system.
- Marking tasks done based on time triggers or events from other applications.
- Streamlining project updates by programmatically managing todo statuses.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket where the todo resides (number) |
| Todo Id | ID of the todo item to be marked as complete (number) |
Output
The node outputs JSON data representing the updated todo item after it has been marked as complete. This typically includes fields such as the todo's ID, status, completion timestamp, and other metadata reflecting its new state.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint corresponding to the authenticated user's account and specified bucket.
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Todo Id will cause the operation to fail.
- Authentication errors if the API key or OAuth token is invalid or expired.
- Permission errors if the authenticated user does not have access to the specified bucket or todo.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and update the API credentials.
- "Not Found" or "Todo or Bucket does not exist": Verify that the provided Bucket Id and Todo Id are correct and accessible.
- "Forbidden": Ensure the authenticated user has sufficient permissions to modify the todo.