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 operation "Get Many" for the OKR Key Result resource retrieves multiple key results associated with objectives in an OKR (Objectives and Key Results) system. This operation is useful when you want to list or filter key results, for example, to display progress on various objectives or to analyze performance metrics across different objectives.
Typical use cases include:
- Fetching all key results linked to a specific objective to monitor its progress.
- Retrieving a paginated list of key results sorted by ID or title.
- Simplifying the response data for easier consumption in workflows or returning raw API responses for advanced processing.
Properties
| Name | Meaning |
|---|---|
| Objective ID | Filter key results by a specific objective ID. Enter the ID to retrieve only related key results. |
| 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 "Title". |
| Limit | Maximum number of results to return (minimum 1). |
| Page | Page number for pagination, allowing retrieval of subsequent result sets. |
Output
The output is a JSON array where each element represents a key result object. The structure depends on whether the "Simplify" property is set:
- If Simplify is
true, the output contains a streamlined version of key result data, focusing on essential fields for easier use in workflows. - If Simplify is
false, the output includes the full raw API response, which may contain additional metadata and nested information.
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 service's availability and correct API permissions to fetch OKR key results.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an incorrect Objective ID may result in empty results or errors.
- Pagination parameters (Limit and Page) must be positive integers; invalid values may cause request failures.
- Sorting fields and directions must match allowed options; otherwise, the API might reject the request.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; reconfigure credentials.
- "Resource not supported" or "Operation not supported" errors suggest misconfiguration of resource or operation parameters.
- API rate limits or network issues can cause timeouts or failed requests; retry after some time or check connectivity.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and data structures)
- n8n Documentation (for configuring credentials and using custom nodes)