Actions101
- Attendance Actions
- Client Actions
- Department Actions
- Designation Actions
- Employee Actions
- Holiday Actions
- KPI Actions
- KPI Category Actions
- KPI Data Actions
- Lead Actions
- Leave Actions
- OKR Key Result Actions
- OKR Objective Actions
- Performance Cycle Actions
- Project Actions
- Project Category Actions
- Task Actions
- Task Category Actions
- Ticket Actions
- Ticket Agent Actions
- Ticket Channel Actions
- Ticket Type Actions
Overview
The node provides integration with the Flowyteam API to manage tasks, specifically supporting the "Get Many" operation for the Task resource. This operation allows users to retrieve multiple task records from Flowyteam with various filtering, sorting, and pagination options.
This node is beneficial in scenarios where you want to automate workflows involving task management, such as:
- Fetching all or a subset of tasks assigned to specific users or clients.
- Retrieving tasks filtered by status, priority, category, or date ranges.
- Integrating task data into reporting dashboards or other systems.
- Automating follow-ups or notifications based on task due dates or statuses.
For example, you could use this node to get all high-priority tasks assigned to a particular user that are due today or earlier, then trigger reminders or escalate overdue items.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching tasks or limit the number of results. |
| Limit | Maximum number of tasks to return (used if Return All is false). |
| Page | Page number for paginated results (used if Return All is false). |
| Simplify | Whether to return simplified task data or the raw API response. |
| Sort Direction | Direction to sort the results: Ascending or Descending. |
| Sort Field | Field to sort by: ID or Title. |
| Additional Fields | Collection of optional filters to narrow down the tasks returned: |
| - Assigned To | Filter tasks assigned to a specific user ID. |
| - Category | Filter tasks by task category ID. |
| - Client ID | Filter tasks associated with a specific client ID. |
| - Created By (Owned By) | Filter tasks created by a specific user ID. |
| - End Date | Filter tasks up to this end date (inclusive). |
| - Priority | Filter by task priority: All, High, Medium, Low. |
| - Search | Search term to filter tasks by text. |
| - Show Due Date Tasks | Whether to show only tasks with due dates less than or equal to today. |
| - Start Date | Filter tasks from this start date (inclusive). |
| - Status | Filter by task status: All, Completed, In Progress, Incomplete, Under Review. |
Output
The node outputs an array of task objects in the json output field. The structure depends on whether the "Simplify" option is enabled:
- If Simplify is true (default), the output contains a streamlined version of each task with key properties for easier consumption in workflows.
- If Simplify is false, the output includes the full raw API response for each task, which may contain additional metadata and nested details.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Flowyteam API via an API authentication token configured in n8n credentials.
- The node depends on the Flowyteam API being accessible and the user having appropriate permissions to read task data.
- No additional external services or environment variables are required beyond the API credential.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., non-existent user IDs or category IDs) may result in empty responses or errors.
- Pagination parameters (Limit and Page) must be positive integers; otherwise, the API may reject the request.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
- Validation errors may occur if filter fields have incorrect formats (e.g., invalid date strings).
- "Operation not supported" errors indicate misuse of the node with unsupported operations or resources.
Resolution tips:
- Verify API credentials and permissions.
- Double-check filter values and ensure they exist in the Flowyteam system.
- Use the "Return All" option carefully to avoid large data loads.
- Inspect raw API responses by disabling "Simplify" to debug unexpected data issues.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and data models)
- n8n documentation on Creating Custom Nodes for further customization guidance