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 to manage company holidays. Specifically, the "Holiday" resource with the "Get Many" operation allows users to retrieve multiple holiday records from the system. This operation supports pagination, sorting, and filtering by year.
This node is beneficial in scenarios where you want to automate workflows that depend on company holidays, such as scheduling, leave management, or reporting. For example, you could use it to fetch all holidays for a given year to automatically block those dates in a calendar or to calculate working days excluding holidays.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all holiday records or limit the number of results |
| Sort Field | Field to sort the results by; options are: "ID" or "Occasion" |
| Limit | Maximum number of holiday records to return (only used if "Return All" is false) |
| Page | Page number for paginated results (only used if "Return All" is false) |
| Additional Fields | Collection of optional filters; currently supports: |
| - Year | Filter holidays by a specific year (number between 2000 and 2100) |
Output
The output is an array of JSON objects representing holiday records retrieved from the Flowyteam API. Each object typically contains details about a holiday such as its ID, occasion name, date, and possibly other metadata depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Flowyteam API.
- The node depends on the Flowyteam API being accessible and properly configured.
- No additional environment variables or external services are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Pagination parameters (
LimitandPage) must be positive integers; invalid values may cause errors or unexpected results. - Filtering by year requires a valid year within the supported range (2000–2100); out-of-range values might result in empty responses.
- If the API key credential is missing or invalid, the node will fail to authenticate and return errors.
- Network connectivity issues can prevent successful API calls.
- Pagination parameters (
Error Messages:
- Errors related to unsupported operations or resources will indicate that the selected operation/resource combination is not supported.
- Authentication errors will typically mention invalid credentials or unauthorized access.
- API rate limits or server errors from Flowyteam may also surface as error messages; retrying after some time or checking API usage limits is recommended.
Links and References
- Flowyteam Official Website
- Flowyteam API Documentation (Assumed typical location; verify actual URL)
- n8n Documentation on Creating Custom Nodes