Overview
The node "Cloodo HRM" integrates with the Cloodo HRM system via its API, allowing users to interact with employee and leave data. Specifically, for the Employee - GET operation, it retrieves detailed information about a single employee by their unique ID. This is useful in scenarios where you need to fetch up-to-date employee details for workflows such as HR management, payroll processing, or internal directory updates.
For example, you might use this node to:
- Retrieve an employee's profile before updating their records.
- Fetch employee details to generate reports or send notifications.
- Validate employee existence and status during onboarding automation.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the employee resource to retrieve. This is a required string input specifying which employee's data to fetch. |
Output
The node outputs JSON data representing the employee's details as returned by the Cloodo HRM API. This typically includes fields such as employee name, contact information, position, department, employment status, and other relevant HR attributes.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the employee, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Cloodo HRM API endpoint at
https://erp-amz.cloodo.com/v4. - Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on the bundled modules handling Employee operations (
CloodoHRMEmployee) and Leave operations (CloodoHRMLeave), though only Employee is relevant here.
Troubleshooting
- Missing or invalid ID: Since the ID property is required, omitting it or providing an incorrect value will likely cause the API call to fail or return no data. Ensure the ID corresponds to an existing employee.
- Authentication errors: If the API key or token is missing, expired, or incorrect, the node will fail to authenticate. Verify credential setup in n8n.
- Network issues: Connectivity problems to the Cloodo HRM API endpoint can cause timeouts or errors. Check network access and endpoint availability.
- Unexpected API responses: Changes in the API schema or permissions may result in incomplete or malformed data. Review API documentation and update node configuration accordingly.
Links and References
- Cloodo HRM API Documentation (assumed base URL; consult official docs for full API reference)
- n8n Documentation on Creating Custom Nodes