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 among other resources. Specifically, for the Task - Create operation, it allows users to create a new task in the Flowyteam system by specifying key details such as the task heading, user ID, start and due dates, priority, and additional optional fields.
This node is beneficial in scenarios where you want to automate task creation within your workflows, for example:
- Automatically creating follow-up tasks when a client interaction occurs.
- Scheduling tasks based on project milestones or deadlines.
- Creating recurring tasks with specific repeat settings.
Properties
| Name | Meaning |
|---|---|
| Heading | The heading/title of the task (required). |
| User ID | The ID of the user who is creating the task (required). |
| Start Date | The start date for the task in MM/DD/YYYY format (required). |
| Due Date | The due date for the task in MM/DD/YYYY format (required). |
| Priority | The priority level of the task (required). Options: Low, Medium, High, Critical. |
| Additional Fields | A collection of optional fields to further specify the task: |
| - Category ID | The ID of the task category. |
| - Dependent Task ID | The ID of another task that this task depends on. |
| - Description | A detailed description of the task. |
| - Employee Access | Comma-separated list of employee IDs who have access to the task. |
| - Image URL | URL of an image associated with the task. |
| - Key Results ID | The ID of related key results (OKRs). |
| - Project ID | The ID of the project this task belongs to. |
| - Repeat Count | Number of times the task should repeat (default "1"). |
| - Repeat Cycles | The number of cycles for repeating the task. |
| - Repeat Type | The type of repeat cycle. Options: Day, Week, Month, Year (default "day"). |
| - Task Boards | Setting related to task boards (default "0"). |
Output
The node outputs JSON data representing the created task object returned from the Flowyteam API. This typically includes all the task details such as its unique ID, heading, dates, priority, and any additional fields set during creation.
No binary data output is involved in 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 provided user ID and other referenced IDs (e.g., projectId, categoryId) being valid within the Flowyteam system.
Troubleshooting
- Invalid Dates: Ensure that the startDate and dueDate are provided in the correct MM/DD/YYYY format; otherwise, the API may reject the request.
- Missing Required Fields: The node requires
heading,userId,startDate,dueDate, andpriority. Omitting these will cause errors. - Invalid IDs: Using invalid or non-existent IDs for user, project, category, or dependent tasks can result in API errors.
- API Authentication Errors: If the API key or token is missing or incorrect, the node will fail to authenticate.
- Repeat Fields Misconfiguration: If repeatCount or repeatType values are invalid or inconsistent, the task creation might fail or behave unexpectedly.
To resolve errors, verify input data correctness, ensure proper API credentials, and check the Flowyteam API documentation for field constraints.
Links and References
- Flowyteam Official Website
- Flowyteam API Documentation (Assumed typical location for API docs)