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 Get operation, the node retrieves detailed information about a specific performance cycle by its ID.
This is useful in scenarios where you want to fetch data about a particular performance evaluation period or cycle within an organization, such as retrieving details for reporting, analysis, or further processing in an automation workflow.
Practical example:
- Fetching a performance cycle's details to include in an employee review report.
- Retrieving performance cycle data to trigger notifications or reminders based on cycle status or dates.
Properties
| Name | Meaning |
|---|---|
| Performance Cycle ID | The unique identifier (ID) of the performance cycle to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the requested performance cycle. The structure typically includes all relevant fields describing the performance cycle, such as its ID, name, start and end dates, status, and any other metadata provided by the Flowyteam API.
If multiple items are returned (not typical for a single "get" operation), they are output as an array of JSON objects.
The node does not output binary data for 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 API being accessible and the provided Performance Cycle ID being valid.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid or missing Performance Cycle ID: The node requires a valid ID; ensure the ID is correctly provided and exists in Flowyteam.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or connectivity issues: Ensure that n8n can reach the Flowyteam API endpoint.
- Unsupported operation or resource errors: These occur if the resource or operation parameters are incorrect; confirm that "performanceCycle" resource and "get" operation are selected.
- Unexpected API response: If the API returns an error or unexpected data, check the Flowyteam API documentation and logs for more details.
Links and References
- Flowyteam Official Website
- Flowyteam API Documentation (Assumed location; replace with actual if known)
- n8n Documentation: Creating Custom Nodes