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 manage to-do lists within projects (called buckets). Specifically, the "Trash a to-Do List" operation allows users to move a specified to-do list into the trash, effectively marking it for deletion or removal from active use. This is useful in scenarios where you want to clean up or archive old or irrelevant to-do lists without permanently deleting them immediately.
Practical examples:
- Archiving completed project task lists to keep the workspace tidy.
- Removing obsolete to-do lists from a project while retaining the option to restore them later.
- Automating cleanup of to-do lists based on certain criteria or workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) that contains the to-do list. Used in the API path. |
| todolistId | The numeric ID of the to-do list to be trashed. Used in the API 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 output JSON contains the response from the Basecamp API after attempting to trash the specified to-do list. If "Return Full Response" is set to false, only the response body is returned, typically confirming the success or failure of the trash operation. If true, the output includes the full HTTP response details such as status code and headers along with the body.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Basecamp API.
- The node uses the Basecamp API endpoint structured as
https://3.basecampapi.com/{accountId}where{accountId}is provided by the user's credentials. - Proper permissions on the Basecamp account are necessary to modify to-do lists.
Troubleshooting
- Invalid Project or To-Do List ID: If the provided IDs do not exist or the user lacks access, the API will return an error. Verify the IDs and permissions.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly configured.
- API Rate Limits: Excessive requests may trigger rate limiting by Basecamp. Implement retry logic or reduce request frequency.
- Return Full Response Misuse: Setting "Return Full Response" to true changes the output format; downstream nodes must handle this accordingly.
Common error messages:
- 404 Not Found: The specified project or to-do list does not exist.
- 401 Unauthorized: Authentication failed due to invalid or missing credentials.
- 403 Forbidden: Insufficient permissions to trash the to-do list.
Resolving these usually involves checking input parameters, verifying credentials, and ensuring proper API access rights.