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 retrieve a specific to-do list within a project (referred to as a "bucket" in Basecamp terminology). It is useful when you want to fetch detailed information about a particular to-do list, such as its tasks, status, and metadata. Common scenarios include automating project management workflows, syncing to-do lists with other tools, or generating reports based on task lists.
For example, you might use this node to:
- Automatically pull the current state of a to-do list for a project dashboard.
- Trigger follow-up actions based on the contents or status of a to-do list.
- Integrate Basecamp to-do lists with external task tracking or notification systems.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the to-do list resides. Used in the API endpoint path. |
| To-Do List ID | The ID of the specific to-do list to retrieve. Used in the API endpoint path. |
| Return Full Response | Whether to return the full HTTP response including status code and headers, or just the body. |
Output
The node outputs JSON data representing the requested to-do list. This includes all details provided by the Basecamp API for that to-do list, such as its name, description, completion status, associated tasks, and metadata.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, which contains:
- Status code of the API request.
- Response headers.
- The JSON body with the to-do list data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and to-do list IDs.
- The Basecamp account ID must be configured in the credentials to construct the correct API base URL.
Troubleshooting
- Invalid Project or To-Do List ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify the IDs before running the node.
- Authentication Errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to access the specified project and to-do list.
- API Rate Limits: Frequent requests may hit Basecamp's rate limits, resulting in errors. Implement retries or backoff strategies if needed.
- Return Full Response Confusion: When enabling "Return Full Response," users should be aware that the output structure changes from just the to-do list JSON to a more complex object containing status and headers.