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 integrates with the Flowyteam API to manage OKR (Objectives and Key Results) objectives. Specifically, the "Delete" operation for the "OKR Objective" resource allows users to remove an existing objective by its unique identifier. This is useful in scenarios where objectives are no longer relevant or were created in error and need to be cleaned up from the system.
Practical examples include:
- Automatically deleting obsolete objectives as part of a workflow cleanup.
- Removing objectives that have been completed or cancelled.
- Managing objectives programmatically based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Objective ID | The ID of the objective to delete |
The property "Objective ID" is required and must be provided as a string representing the unique identifier of the objective to be deleted.
Output
The output of this operation is JSON data returned from the Flowyteam API after attempting to delete the specified objective. Typically, this will contain confirmation of deletion or details about the deleted objective. The exact structure depends on the API response but generally includes status information.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires an API authentication token or API key credential configured in n8n to authorize requests.
- The node depends on the Flowyteam API endpoints for managing OKR objectives.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Objective ID will likely result in an error from the API indicating the objective was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
Error messages and resolutions:
- "Objective not found": Verify that the Objective ID is correct and exists in the Flowyteam system.
- Authentication errors: Check that the API key or token is correctly set up and has sufficient permissions.
- Timeouts or network errors: Ensure stable internet connection and that the Flowyteam API endpoint is reachable.
Links and References
- Flowyteam API documentation (refer to the official docs for detailed API usage and responses)
- n8n documentation on creating custom nodes and using API credentials