Overview
The node "Cloodo HRM" integrates with the Cloodo HRM system via its API, allowing users to manage HR-related data such as employees and leaves. Specifically, the Employee - UPDATE operation enables updating details of an existing employee record by specifying the employee's ID and any fields to modify.
This node is beneficial in scenarios where automated workflows need to keep employee information up-to-date, such as syncing HR databases, updating employee status after onboarding or offboarding, or modifying department/designation assignments based on organizational changes.
Example use cases:
- Automatically update an employee’s email and designation when their role changes.
- Change the status of an employee to "Deactive" upon termination.
- Modify department assignment for an employee after internal transfers.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the employee to update (required). |
| Additional Fields | A collection of optional fields to update for the employee: |
| - Name | Employee's full name (string). |
| Employee's email address (string). | |
| - Department ID | Identifier of the department the employee belongs to (string). |
| - Designation ID | Identifier of the employee's job designation or title (string). |
| - Status | Employment status; options are "Active" or "Deactive". |
Output
The node outputs JSON data representing the updated employee record as returned by the Cloodo HRM API. This typically includes the employee's current details after the update operation.
If the API supports it, the output may also include metadata such as update timestamps or confirmation messages. There is no indication that binary data is involved in this operation.
Dependencies
- Requires an active connection to the Cloodo HRM API endpoint at
https://erp-amz.cloodo.com/v4. - Needs a valid API authentication token or key configured in the node credentials to authorize requests.
- The node expects JSON content-type headers and uses standard RESTful HTTP methods.
Troubleshooting
- Invalid or missing ID: The update operation requires a valid employee ID. Ensure the ID field is correctly set and corresponds to an existing employee.
- Authentication errors: If the API key or token is invalid or expired, the node will fail to authenticate. Verify credentials in the node settings.
- Invalid field values: Providing incorrect formats (e.g., non-string for email) or invalid option values for status may cause API errors. Validate input data before execution.
- Network issues: Connectivity problems to the API endpoint can cause timeouts or failures. Check network access and API availability.
- API response errors: The API might return error messages if the employee does not exist or if there are permission issues. Review the error message details to adjust inputs or permissions accordingly.
Links and References
- Cloodo HRM API Documentation (Assumed URL based on baseURL, verify actual docs)
- n8n Documentation on Creating Custom Nodes