Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation retrieves todo lists from a specified project bucket and todo set within the Basecamp service. It allows filtering the todo lists by their status, such as active, archived, or trashed. This is useful for project management workflows where you want to programmatically access and process task lists based on their current state.
Practical examples include:
- Automatically fetching all active todo lists in a project to generate reports.
- Archiving completed todo lists by identifying those with "archived" status.
- Cleaning up trashed todo lists by listing them before deletion.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric ID of the project bucket containing the todo sets. |
| Todoset Id | The numeric ID of the specific todo set within the bucket to retrieve todo lists from. |
| Status | Filter to select todo lists by their status. Options: Active, Archived, Trashed. |
Output
The output contains JSON data representing the todo lists retrieved from the specified bucket and todo set, filtered by the chosen status. Each item in the output JSON typically includes details about individual todo lists such as their IDs, titles, status, and other metadata provided by the Basecamp API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the authenticated user's Basecamp account ID.
- Proper configuration of the API credentials and permissions to access the specified buckets and todo sets is necessary.
Troubleshooting
- Invalid Bucket or Todoset ID: If the provided IDs do not exist or the user lacks permission, the node may return errors or empty results. Verify the IDs and user access rights.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Status Filter Issues: Using an unsupported status value might result in no data returned. Use only the provided options: active, archived, trashed.
- API Rate Limits: Excessive requests may trigger rate limiting by Basecamp. Implement retry logic or reduce request frequency if needed.