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 various HR and project management resources, including Performance Cycles. Specifically, for the Performance Cycle resource with the Create operation, it allows users to create a new performance cycle by specifying its name, type, start date, and end date.
This is useful in scenarios where organizations want to automate the creation of performance evaluation periods (cycles) such as monthly, quarterly, semi-annually, or annually. For example, an HR team can use this node to programmatically set up performance cycles that align with their review schedules, enabling automated tracking and reporting within their workflows.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the performance cycle to be created. |
| Cycle Type | The type of the performance cycle. Options: Monthly, Quarterly, Semi-Annually, Annually. |
| Start Date | The start date of the performance cycle (format MM/DD/YYYY). |
| End Date | The end date of the performance cycle (format MM/DD/YYYY). |
Output
The output of the node after creating a performance cycle will be a JSON object representing the newly created performance cycle record as returned by the Flowyteam API. This typically includes fields such as the unique identifier of the cycle, its name, type, start and end dates, and possibly metadata like creation timestamps.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires configuration of an API authentication credential (e.g., an API key or token) within n8n to authorize requests to the Flowyteam service.
- The node depends on the Flowyteam API endpoints for managing performance cycles.
Troubleshooting
Common Issues:
- Invalid or missing required properties (e.g., missing name or dates) will cause the API request to fail.
- Incorrect date formats may lead to errors; ensure dates are provided in MM/DD/YYYY format.
- Authentication failures if the API credential is not configured correctly or has expired.
- Network connectivity issues preventing access to the Flowyteam API.
Error Messages:
- Errors related to missing required parameters: Verify all required fields are filled.
- Authentication errors: Check API credentials and permissions.
- API response errors indicating invalid data: Validate input values, especially dates and cycle type.
Resolving these usually involves verifying input data correctness, ensuring proper credential setup, and confirming network connectivity.
Links and References
- Flowyteam Official Website
- Flowyteam API Documentation (refer to your organization's internal or public API docs for detailed endpoint info)
- n8n Documentation on Credentials and HTTP Request Nodes for API integrations