Cloodo HRM icon

Cloodo HRM

Interact with HttpBin API

Overview

The node integrates with the Cloodo HRM system to manage employee data. Specifically, the Employee - CREATE operation allows users to add a new employee record into the HRM system. This is useful for automating onboarding processes, syncing employee databases, or integrating HR workflows within an automation pipeline.

Practical examples include:

  • Automatically creating employee profiles when a new hire is added in an applicant tracking system.
  • Syncing employee data from other internal systems into Cloodo HRM.
  • Setting up employee accounts with initial status, department, and designation details programmatically.

Properties

Name Meaning
Name The full name of the employee to be created.
Email The email address of the employee.
Password The password for the employee's account (input masked).
Email Notifications Whether the employee should receive email notifications (true/false).
Status The login status of the employee; options are "Enable" or "Disable".
Gender The gender of the employee; options are "Male" or "Female".
Employee Account The unique account identifier for the employee.
Format Date The date format used for the joining date; currently supports "Y-M-D" (e.g., 2022-11-11).
Joining Date The date the employee joined the company.
Department ID Identifier for the department the employee belongs to.
Designation ID Identifier for the employee's job designation or role.

Output

The node outputs JSON data representing the newly created employee record as returned by the Cloodo HRM API. This typically includes all submitted fields along with any additional metadata or identifiers assigned by the system.

If the node supports binary data output (not evident from the provided code), it would represent attachments or files related to the employee, but no such indication exists here.

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.
  • The node expects JSON content-type headers for requests and responses.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Validation errors: Required fields like Name, Email, Password, Department ID, and Designation ID must be provided and valid.
  • Date format issues: The joining date must conform to the selected date format (y-MM-dd).
  • API connectivity: Network issues or incorrect base URL configuration can cause request failures.
  • Status field: Only "enable" or "disable" are accepted values; invalid inputs will cause errors.

Links and References

Discussion