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, allowing users to manage various resources related to workforce and project management. Specifically, for the Performance Cycle resource with the Delete operation, this node enables the deletion of a specified performance cycle by its unique identifier.
This is useful in scenarios where an organization needs to remove outdated or incorrect performance cycles from their system to maintain accurate records. For example, if a performance review period was created by mistake or is no longer relevant, this node can be used to delete it programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Performance Cycle ID | The unique identifier (ID) of the performance cycle to delete. This is a required string input. |
Output
The output of the node after deleting a performance cycle will be JSON data representing the result of the deletion request. Typically, this might include confirmation of successful deletion or details about the deleted entity depending on the API response.
No binary data output is indicated for 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 endpoint responsible for deleting performance cycles.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Performance Cycle ID will likely cause the API to return an error.
- Missing or incorrect API credentials will prevent the node from authenticating with the Flowyteam API.
- Network connectivity issues may cause timeouts or failures in reaching the API.
Error Messages:
- Errors indicating "Performance Cycle not found" suggest the provided ID does not exist; verify the ID.
- Authentication errors indicate problems with the API key or token; check credential configuration.
- Generic HTTP errors (e.g., 400, 401, 404, 500) should be investigated based on the API documentation and logs.
Links and References
- Flowyteam API Documentation (for Performance Cycle endpoints) — consult the official API docs for detailed information on request/response formats and error codes.
- n8n Documentation on creating custom nodes and using API credentials.