Overview
This node integrates with the Cloodo HRM system to manage employee leave records. Specifically, the "Leave - Create" operation allows users to create a new leave request for an employee by specifying details such as the user ID, type of leave, leave date, duration, reason, and status.
Common scenarios where this node is beneficial include automating leave management workflows, integrating leave requests into broader HR or project management systems, and streamlining employee absence tracking.
For example, an HR automation workflow could use this node to automatically submit leave requests on behalf of employees based on inputs from other systems or forms.
Properties
| Name | Meaning |
|---|---|
| UserID | The unique identifier of the employee requesting leave. |
| TypeId | The type/category of leave being requested (e.g., vacation, sick leave). |
| Leave Date | The date format option for specifying the leave date. Currently supports "Y-M-D" format. |
| Duration | The length or portion of the leave: Single day, Multiple days, First half-day, or Second half-day. |
| Reason | The explanation or justification for the leave request. |
| Status | The current status of the leave request. Options are Pending, Rejected, or Approved. |
Output
The node outputs JSON data representing the newly created leave record as returned by the Cloodo HRM API. This typically includes confirmation details such as leave ID, timestamps, and the submitted properties.
No binary data output is indicated in the source code.
Dependencies
- Requires an active connection to the Cloodo HRM API endpoint at
https://erp-amz.cloodo.com/v4. - Requires an API authentication credential configured in n8n (an API key or token).
- The node depends on internal modules handling Employee and Leave operations, but these are bundled internally.
Troubleshooting
- Invalid or missing required fields: Ensure all required properties (UserID, TypeId, Duration, Reason, Status) are provided and correctly formatted.
- API authentication errors: Verify that the API credential is valid and has sufficient permissions.
- Incorrect status value: Note that the "Approved" status option incorrectly maps to "rejected" in the provided options; this may cause unexpected behavior. Confirm and correct the status values if necessary.
- Date format issues: The node currently supports only one date format option ("Y-M-D"). Providing dates in other formats may lead to errors.
- Network or API downtime: Check connectivity and API availability if requests fail.
Links and References
- Cloodo HRM Official Website
- Cloodo HRM API Documentation (if publicly available)
- n8n Documentation on Creating Custom Nodes