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
This node interacts with the Flowyteam API to manage OKR (Objectives and Key Results) key results. Specifically, the "Get" operation for the "OKR Key Result" resource retrieves detailed information about a specific key result by its ID. This is useful in scenarios where you want to fetch the current state or details of a particular key result within an OKR framework, such as tracking progress or displaying key result data in dashboards or reports.
Practical examples:
- Fetching a key result's details to display its current progress in a project management workflow.
- Retrieving key result information to trigger conditional logic based on its status or metrics.
- Integrating OKR data into other systems by pulling key result details dynamically.
Properties
| Name | Meaning |
|---|---|
| Key Result ID | The unique identifier of the key result to retrieve. |
Output
The node outputs JSON data representing the requested key result's details. This typically includes all relevant fields returned by the Flowyteam API for a key result, such as its title, description, progress metrics, associated objective, deadlines, and status.
If multiple items are returned (though for "get" it is usually a single item), they will be output as an array of JSON objects.
The node does not output binary data.
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 service being available and responsive.
Troubleshooting
Common issues:
- Invalid or missing Key Result ID: The node requires a valid key result ID; providing an incorrect or empty ID will cause errors.
- Authentication failures: If the API key or token is invalid or expired, the node will fail to authenticate.
- Network or API downtime: Connectivity issues or Flowyteam API outages will prevent successful retrieval.
Error messages:
- Errors indicating "Key Result not found" suggest the provided ID does not exist.
- Authentication errors indicate problems with the API credentials.
- Timeout or network errors indicate connectivity issues.
Resolutions:
- Verify the Key Result ID is correct and exists in Flowyteam.
- Check and update the API credentials in n8n.
- Ensure network connectivity and that the Flowyteam API is operational.
Links and References
- Flowyteam official API documentation (refer to their site for detailed API endpoints and data structures).
- n8n documentation on creating and using custom nodes with API credentials.