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 interacts with the Basecamp API to mark a specific to-do item as "uncompleted" within a given project (referred to as a bucket in Basecamp). It is useful when you want to revert the completion status of a task, for example, if a task was marked done by mistake or needs to be reopened for further work.
Common scenarios include:
- Project management workflows where tasks need to be reopened.
- Automation that adjusts task statuses based on external triggers or conditions.
- Synchronizing task states between Basecamp and other tools.
Example: You have a to-do item in a project that was accidentally completed. Using this node operation, you can programmatically set it back to incomplete without manually changing it in the Basecamp interface.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the to-do. Used in the API endpoint path. |
| todoId | The numeric ID of the to-do item to mark as uncompleted. Used in the API endpoint path. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after marking the to-do as uncompleted. This typically includes the updated to-do item's details such as its current completion status and metadata.
If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code and headers, which can be useful for debugging or advanced workflows.
No binary data is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The user must provide valid credentials with access rights to the specified project and to-do items.
- The node uses the Basecamp API base URL constructed dynamically from the user's account ID.
Troubleshooting
- Invalid Project ID or To-do ID: If the IDs provided do not exist or the user lacks permission, the API will return an error. Verify the IDs and permissions.
- Authentication Errors: Ensure the OAuth2 credentials are valid and have not expired.
- API Rate Limits: Basecamp may limit the number of requests; handle rate limiting errors by retrying after some delay.
- Return Full Response Misuse: If enabled but not handled properly downstream, the full response object might cause issues in subsequent nodes expecting only JSON data.