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) objectives. Specifically, the "Get" operation for the "OKR Objective" resource retrieves detailed information about a single objective by its unique identifier. This is useful in scenarios where you want to fetch the current state or details of a specific objective within your organization's OKR framework.
Practical examples include:
- Fetching an objective's details to display in a dashboard.
- Retrieving an objective before updating it.
- Using the objective data as part of a workflow that tracks progress or sends notifications.
Properties
| Name | Meaning |
|---|---|
| Objective ID | The unique identifier of the objective to retrieve. This is required to specify which objective to get. |
Output
The node outputs JSON data representing the requested OKR objective. The structure typically includes all relevant fields of the objective such as its ID, title, description, status, start and end dates, and any other metadata provided by the Flowyteam API for an objective.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The node depends on the Flowyteam API endpoints for OKR objectives.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Objective ID will likely result in an error or empty response.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Errors indicating "Objective not found" suggest the Objective ID does not exist.
- Authentication errors indicate problems with the API key or token.
- Timeout or network errors require checking connectivity and API availability.
To resolve these, verify the Objective ID correctness, ensure valid API credentials are set up, and confirm network access to the Flowyteam API.
Links and References
- Flowyteam API documentation (for OKR Objectives): [Refer to Flowyteam official API docs]
- n8n documentation on creating custom nodes and using API credentials.