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 organizational resources, including performance cycles. Specifically, for the Performance Cycle resource, the Update operation allows users to modify an existing performance cycle's details such as its name, type, start date, and end date. This is useful in scenarios where performance evaluation periods need adjustment due to changes in company policies or scheduling.
Practical examples include:
- Updating the dates of a quarterly performance review cycle after a shift in fiscal calendar.
- Changing the name or type of a performance cycle to reflect new evaluation criteria.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the performance cycle. |
| 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). |
| Performance Cycle ID | The unique identifier of the performance cycle to update. |
Output
The node outputs JSON data representing the updated performance cycle object returned by the Flowyteam API. This typically includes all relevant fields of the performance cycle such as its ID, name, type, start and end dates, and possibly metadata about the update operation.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The node depends on the Flowyteam API endpoints for updating performance cycles.
Troubleshooting
Common issues:
- Invalid or missing Performance Cycle ID will cause the update to fail.
- Incorrect date formats for start or end dates may result in API errors.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Attempting to update a non-existent performance cycle will return an error.
Error messages and resolutions:
- "Performance Cycle not found": Verify that the provided Performance Cycle ID is correct.
- "Invalid date format": Ensure dates are provided in MM/DD/YYYY format.
- "Unauthorized" or "Authentication failed": Check that the API key or token is valid and properly configured.
- "Missing required fields": Confirm all required properties (Name, Cycle Type, Start Date, End Date, Performance Cycle ID) are supplied.
Links and References
- Flowyteam API Documentation (general reference for API endpoints)
- n8n Documentation for configuring API credentials and using custom nodes