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 integrates with the Basecamp API to manage to-dos within projects (called buckets in Basecamp). Specifically, the "Complete a to-Do" operation marks a specified to-do item as completed within a given project. This is useful for automating task management workflows, such as updating task statuses based on external triggers or batch processing task completions.
Practical examples include:
- Automatically marking tasks as done when a related event occurs in another system.
- Syncing task completion status from an external project management tool.
- Bulk completing multiple to-dos via automation without manual intervention.
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 be marked as complete. 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 attempting to complete the to-do. If "Return Full Response" is set to false, the output contains only the response body, typically including details about the updated to-do item. If true, the output includes the entire HTTP response, which can contain status codes and headers alongside the body.
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 base URL constructed dynamically using the account ID from credentials.
- Proper permissions on the Basecamp account are necessary to modify to-dos.
Troubleshooting
Common issues:
- Invalid or missing Project ID or To-Do ID will cause the API call to fail.
- Insufficient permissions or expired API tokens may result in authorization errors.
- Network connectivity problems can prevent successful API communication.
Error messages:
- 404 Not Found: The specified project or to-do does not exist. Verify IDs.
- 401 Unauthorized: Authentication failed. Check API credentials.
- 400 Bad Request: Malformed request, possibly due to invalid parameters.
To resolve these, ensure that the provided IDs are correct, the API credentials are valid and have sufficient rights, and that the network connection is stable.