Cloodo HRM icon

Cloodo HRM

Interact with HttpBin API

Overview

The node integrates with the Cloodo HRM system, specifically allowing users to update leave records. It is useful in scenarios where HR or management systems need to programmatically modify employee leave details such as dates, duration, reasons, and status. For example, an HR automation workflow could update a leave request's status from "Pending" to "Approved" after managerial approval.

Properties

Name Meaning
ID The unique identifier of the leave record to update (required).
Additional Fields Optional fields to update on the leave record:
- UserID Identifier of the user associated with the leave.
- TypeID Identifier for the type/category of leave.
- Leave Date The date of the leave.
- Duration Length of the leave; options are: Single, Multiple, First Half, Second Half.
- Reason Textual reason or explanation for the leave.
- Status Current status of the leave request; options are Pending, Rejected, Approved (note: Approved value seems incorrectly set to "rejected" in source).

Output

The node outputs JSON data representing the updated leave record as returned by the Cloodo HRM API. This typically includes all leave properties reflecting the new state after the update operation. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Cloodo HRM API.
  • The base URL for API requests is https://erp-amz.cloodo.com/v4.
  • Proper configuration of the API credential within n8n is necessary for successful communication.

Troubleshooting

  • Common Issues:
    • Incorrect or missing leave ID will cause the update to fail.
    • Invalid or expired API credentials will result in authentication errors.
    • Providing invalid values for enumerated fields like Duration or Status may cause API rejections.
  • Error Messages:
    • Authentication failures usually indicate issues with the API key setup.
    • Validation errors from the API may specify which field is incorrect or missing.
  • Resolution Tips:
    • Verify the leave ID exists before attempting update.
    • Double-check API credentials and permissions.
    • Ensure enumerated fields use valid option values exactly as specified.

Links and References

Discussion