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 enables creating leave requests for users within an organization. It is useful in HR automation workflows where employees submit leave requests, and these requests need to be recorded or processed automatically. For example, it can be used to automate the submission of single-day or multiple-day leave requests with reasons and optional attachments, streamlining leave management.
Properties
| Name | Meaning |
|---|---|
| User ID | ID of the user requesting leave |
| Leave Type ID | ID representing the type of leave (e.g., vacation, sick leave) |
| Duration | Duration of the leave; options are "Single Day" or "Multiple Days" |
| Leave Date | Date of leave in MM/DD/YYYY format; used when duration is "Single Day" |
| Multiple Dates | Comma-separated list of dates in MM/DD/YYYY format; used when duration is "Multiple Days" |
| Reason | Explanation or justification for the leave request |
| Status | Current status of the leave request; options include "Pending", "Approved", "Rejected", "Cancelled" |
| Additional Fields - Attachment | Optional attachment for the leave request, such as a file path or URL |
Output
The node outputs JSON data representing the created leave request record. This typically includes details such as the leave request ID, user ID, leave type, dates, reason, status, and any attachments. The output allows subsequent workflow steps to access and use this information for further processing or notifications.
No binary data output is indicated.
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:
- Invalid or missing User ID or Leave Type ID will cause the request to fail.
- Incorrect date formats (not MM/DD/YYYY) may result in errors or rejected requests.
- Providing both single and multiple dates simultaneously is not supported; ensure only the relevant field is filled based on the duration.
- Network or authentication failures with the Flowyteam API will prevent leave creation.
Error Messages:
- Errors indicating unsupported operations or resources suggest misconfiguration of resource or operation parameters.
- Validation errors from the API about missing required fields should be resolved by ensuring all mandatory properties are provided.
- Authentication errors require checking the API key credential setup.
Links and References
- Flowyteam API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes