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 functionality to retrieve multiple leave records from the Flowyteam API. It is designed to fetch lists of employee leave requests with various filtering, sorting, and pagination options. This operation is useful for HR automation workflows where you need to analyze, report, or process leave data in bulk.
Typical use cases include:
- Generating reports on employee leaves within a specific date range.
- Filtering leaves by status (e.g., approved, pending) for managerial review.
- Searching leaves by employee name or reason.
- Integrating leave data into payroll or attendance systems.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all leave records or limit the number of results. |
| Limit | Maximum number of leave records to return when "Return All" is false. |
| Page | Page number for paginated results when "Return All" is false. |
| Simplify | Whether to return simplified leave data or the raw API response. |
| Sort Field | Field to sort the leave records by; options are: ID or Reason. |
| Additional Fields | Collection of optional filters: - Employee ID: Filter leaves by a specific employee ID. - End Date: Filter leaves up to this end date. - Leave Type ID: Filter by leave type. - Search: Search leaves by employee name or leave reason. - Start Date: Filter leaves from this start date. - Status: Filter leaves by status; options are All, Pending, Approved, Rejected. |
Output
The output is an array of JSON objects representing leave records. Each object contains details about individual leave requests such as employee information, leave type, dates, status, and reason. If the "Simplify" option is enabled, the data is returned in a streamlined format focusing on key fields. Otherwise, the full raw API response is provided.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Flowyteam API.
- The node depends on the Flowyteam service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., wrong date formats or non-existent employee IDs) may result in empty responses or errors.
- Pagination parameters must be positive integers; otherwise, the API might reject the request.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Validation errors on filters suggest checking the input formats and allowed values.
- Network or timeout errors require ensuring connectivity to the Flowyteam API endpoint.
Links and References
- Flowyteam API Documentation (for leave management): https://docs.flowyteam.com/api/leave (example link, replace with actual if available)