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 integrates with the Flowyteam API to manage various HR and project management resources. Specifically, for the Performance Cycle resource with the Get Many operation, it retrieves multiple performance cycle records from the Flowyteam system.
This operation is useful when you want to list or analyze multiple performance cycles, for example:
- Fetching all performance cycles to display in a dashboard.
- Retrieving performance cycles sorted by name or ID for reporting.
- Getting simplified data for quick processing or raw data for detailed analysis.
Properties
| Name | Meaning |
|---|---|
| Simplify | Whether to return simplified response data or the raw API response. (Boolean: true/false) |
| Sort Direction | Direction to sort the results. Options: Ascending, Descending |
| Sort Field | Field to sort by. Options: ID, Name |
Output
The output is an array of JSON objects representing performance cycles retrieved from the API.
- If Simplify is enabled, the output contains a streamlined version of each performance cycle's data, focusing on key fields for easier consumption.
- If Simplify is disabled, the output includes the full raw API response for each performance cycle, which may contain more detailed or nested information.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Flowyteam API via an API key credential configured in n8n.
- The node depends on the Flowyteam API being accessible and the credentials having permission to read performance cycle data.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Network connectivity problems can prevent the node from reaching the Flowyteam API.
- Requesting too many records without pagination might lead to timeouts or rate limiting.
Error messages:
- Authentication failures typically indicate invalid API keys; verify and update credentials.
- "Operation not supported" errors occur if the resource or operation parameters are incorrect.
- API rate limit errors require waiting or adjusting request frequency.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes