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 leave requests within an organization. Specifically, the "Leave" resource with the "Get" operation allows users to retrieve detailed information about a specific leave request by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching the status and details of an employee's leave request for approval workflows.
- Integrating leave data into HR dashboards or reporting tools.
- Automating notifications or follow-ups based on leave request details.
For example, you can use this node to get the details of a leave request by providing its ID, then use that data to update other systems or trigger further automation steps.
Properties
| Name | Meaning |
|---|---|
| Leave Request ID | The unique identifier of the leave request to retrieve. This is required to specify which leave request's details to fetch. |
Output
The node outputs JSON data representing the leave request details retrieved from the Flowyteam API. This typically includes fields such as the leave type, start and end dates, status, employee information, and any comments or metadata associated with the leave request.
No binary data output is involved in 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 service being accessible and the provided leave request ID being valid.
Troubleshooting
- Invalid Leave Request ID: If the provided ID does not exist or is malformed, the node may return an error or empty result. Verify the ID correctness.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to access leave data.
- Network Issues: Connectivity problems with the Flowyteam API will cause failures; check network and API availability.
- Unsupported Operation: Using an unsupported operation for the Leave resource will throw an error indicating the operation is not supported.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Creating Custom Nodes