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 business resources, including KPI Categories. Specifically, for the KPI Category resource and the Get Many operation, it retrieves multiple KPI categories from the Flowyteam system.
This operation is useful when you want to list or process multiple KPI categories at once, for example:
- Displaying all KPI categories in a dashboard.
- Filtering or sorting KPI categories before further processing.
- Synchronizing KPI category data between Flowyteam and another system.
Properties
| Name | Meaning |
|---|---|
| Simplify | Whether to return simplified response data (true) or the raw API response (false). |
| Sort Direction | Direction to sort the results: "Ascending" or "Descending". |
| Sort Field | Field to sort by: "ID" or "Name". |
These properties allow controlling the format and ordering of the retrieved KPI categories.
Output
The output is an array of JSON objects representing KPI categories retrieved from the Flowyteam API.
- If Simplify is enabled, the output contains a simplified version of each KPI category with key fields for easier consumption.
- If Simplify is disabled, the output includes the full raw API response for each KPI category.
No binary data output is involved in 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 KPI categories.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Network connectivity problems can prevent API calls.
- Using unsupported sort fields or directions may result in API errors.
- Requesting data without proper permissions may lead to authorization failures.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- "Resource not supported" or "Operation not supported" errors mean the selected resource or operation is incorrect.
- API rate limits or server errors should be retried after some time.
Links and References
- Flowyteam API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes
- General info on KPI management best practices and use cases.