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
The "Get To-Do Set" operation in the Todoset resource allows users to retrieve detailed information about a specific to-do set within a project (referred to as a "bucket") in Basecamp. This node is useful when you want to fetch the current state, metadata, or contents of a particular to-do set for further processing, reporting, or integration with other tools.
Common scenarios:
- Synchronizing to-do sets from Basecamp into another project management tool.
- Displaying detailed to-do set information in dashboards or reports.
- Automating workflows based on the status or properties of a to-do set.
Practical example:
You have a project with multiple to-do sets and want to automatically pull the details of a specific to-do set to check its progress or update related records in your CRM system.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the to-do set. Used in the API endpoint path. |
| To-Do Set ID | The numeric ID of the to-do set to retrieve. Used in the API endpoint path. |
| Return Full Response | Boolean option to return the full HTTP response including status code, headers, and body instead of only the response body. |
Output
The node outputs JSON data representing the to-do set retrieved from Basecamp. This typically includes all details about the to-do set such as its title, description, creation date, completion status, and possibly nested to-dos within the set.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, which contains:
- Status code
- Headers
- Body (the to-do set data)
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access projects and to-do sets.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential setup.
Troubleshooting
- Invalid Project ID or To-Do Set ID: If either ID is incorrect or does not exist, the API will likely return a 404 Not Found error. Verify that the IDs are correct and that the authenticated user has access to them.
- Authentication errors: Ensure the OAuth2 credentials are valid and have not expired. Re-authenticate if necessary.
- Permission issues: The connected Basecamp account must have permission to view the specified project and to-do set.
- Network or API downtime: Temporary network issues or Basecamp API outages can cause request failures. Retry after some time or check Basecamp status pages.