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 "Create" operation allows users to add new holiday entries into their system. This is useful for automating the management of company-wide holidays, ensuring that workflows and scheduling tools are aware of official non-working days.
Practical examples include:
- Automatically adding public holidays or company-specific holidays to a calendar system.
- Integrating holiday data into HR or attendance systems to prevent scheduling conflicts.
- Triggering notifications or workflow adjustments based on upcoming holidays.
Properties
| Name | Meaning |
|---|---|
| Occasion | The name or description of the holiday (e.g., "Christmas", "Company Foundation Day"). |
| Date | The date of the holiday in DD/MM/YYYY format (e.g., "21/03/2025"). |
Output
The node outputs JSON data representing the created holiday record as returned by the Flowyteam API. This typically includes details such as the holiday's unique identifier, occasion name, date, and possibly metadata about creation time or status.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Flowyteam API.
- Needs an API authentication token or API key credential configured in n8n under the node's credentials.
- The node depends on the Flowyteam service being available and accessible from the environment where n8n runs.
Troubleshooting
Common issues:
- Invalid date format: The "Date" property must be in DD/MM/YYYY format; incorrect formatting may cause API errors.
- Missing required fields: Both "Occasion" and "Date" are mandatory; omitting either will result in an error.
- Authentication failures: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network connectivity problems: The node requires internet access to reach the Flowyteam API endpoint.
Error messages:
- Errors related to invalid input parameters usually indicate missing or malformed "Occasion" or "Date".
- Authentication errors suggest checking the API key credential configuration.
- API response errors might indicate quota limits, permission issues, or server-side problems.
Resolving these generally involves verifying input values, confirming credential setup, and ensuring network connectivity.
Links and References
- Flowyteam official website and API documentation (please refer to your organization's internal resources or the Flowyteam developer portal for detailed API docs).