Overview
This node integrates with the Kaizen app to retrieve multiple tasks based on various filters and options. The "Get Many" operation for the "Task" resource allows users to fetch a list of tasks from their Kaizen account, optionally filtered by criteria such as folder, priority, tags, due date, and more. It supports returning all matching tasks or limiting the number of results.
Common scenarios where this node is beneficial include:
- Synchronizing tasks from Kaizen into other systems or workflows.
- Generating reports or dashboards based on task attributes like priority or completion status.
- Automating follow-ups or reminders by fetching tasks due soon or tagged in specific ways.
Practical example:
- Fetch all incomplete tasks tagged with "urgent" in a specific folder to trigger notifications.
- Retrieve up to 20 high-priority tasks due today for daily planning automation.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching tasks or only up to a specified limit. |
| Limit | Maximum number of tasks to return (used if "Return All" is false). |
| Options | Additional options: |
| Include Completed | Whether to include completed tasks in the results. |
| Filters | Criteria to filter tasks by: |
| Color Tag | Filter tasks by color tag (hex color code). |
| Due Date | Filter tasks by due date (ISO 8601 datetime). |
| Folder ID | Filter tasks by folder identifier. |
| IDs (Comma Separated) | Filter tasks by specific task IDs (comma-separated string). |
| Location | Filter tasks by location string. |
| Priority | Filter tasks by numeric priority value. |
| Tag | Filter tasks by tag string. |
Output
The node outputs an array of task objects in JSON format. Each object represents a task retrieved from Kaizen and includes properties such as title, folder ID, due date, priority, tags, and other task metadata as provided by the Kaizen API.
No binary data output is produced by this operation.
Dependencies
- Requires an authenticated connection to the Kaizen API via an OAuth2-based credential.
- The node makes HTTP requests to the Kaizen cloud functions endpoint (
https://us-central1-kaizen-a1281.cloudfunctions.net/api). - Proper timezone configuration is used to convert date/time inputs to ISO 8601 format.
Troubleshooting
- Empty results: Ensure that the filter criteria are correct and that tasks matching those filters exist in the Kaizen account.
- Authentication errors: Verify that the API authentication token or OAuth2 credentials are valid and have not expired.
- Invalid date formats: Date/time filters must be valid ISO 8601 strings; otherwise, the API may reject the request.
- Limit ignored when Return All is true: If you want to limit results, ensure "Return All" is set to false.
- API rate limits or network issues: Temporary failures may occur; retrying after some time or checking network connectivity can help.
Links and References
- Kaizen App Official Website
- Kaizen API Documentation (Assumed, please verify actual URL)