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
Leave → Update
AI-generatedOverview
The node provides functionality to update leave requests within the Flowyteam system. It allows users to modify details of an existing leave request such as the user requesting leave, type of leave, duration, dates, reason, status, and optional attachments. This is useful in HR automation workflows where leave management needs to be integrated with other systems or automated processes.
Practical examples include:
- Automatically updating leave requests based on external approvals.
- Syncing leave status changes from a third-party HR system.
- Modifying leave details programmatically when correcting errors or adding additional information.
Properties
| Name | Meaning |
|---|---|
| User ID | ID of the user requesting leave |
| Leave Type ID | ID of the leave type |
| Duration | Duration of the leave; options: Single Day, Multiple Days |
| Leave Date | Date of leave (MM/DD/YYYY) - used when duration is Single Day |
| Multiple Dates | Comma-separated list of dates (MM/DD/YYYY,MM/DD/YYYY) - used when duration is Multiple Days |
| Reason | Reason for the leave request |
| Status | Status of the leave request; options: Pending, Approved, Rejected, Cancelled |
| Additional Fields | Collection of optional fields; currently supports: Attachment (file path or URL) |
| Leave Request ID | ID of the leave request to update |
Output
The node outputs JSON data representing the updated leave request record as returned by the Flowyteam API. The structure typically includes all relevant leave request details such as IDs, dates, status, reason, and any attachments.
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 via its API endpoints.
- Proper configuration of the API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Leave Request ID will cause the update operation to fail.
- Incorrect date formats (not MM/DD/YYYY) may result in API errors.
- Providing multiple dates when duration is set to single day or vice versa can cause validation errors.
- Missing required fields like User ID, Leave Type ID, Reason, or Status will prevent successful updates.
Error messages:
- Errors related to authentication usually indicate invalid or missing API credentials.
- Validation errors from the API often specify which field is incorrect or missing.
- Network or connectivity errors suggest issues reaching the Flowyteam API endpoint.
Resolutions:
- Ensure all required fields are correctly filled and formatted.
- Verify API credentials and network connectivity.
- Match the duration property with the appropriate date input (single vs multiple).
Links and References
- Flowyteam official API documentation (refer to your internal or public API docs for detailed endpoint info)
- n8n documentation on creating and using custom nodes and credentials