Overview
The node integrates with the Cloodo HRM system, specifically allowing interaction with employee and leave data via its API. For the Leave - Get operation, it retrieves detailed information about a specific leave record by its ID. This is useful in scenarios where you need to fetch leave details for reporting, auditing, or workflow automation purposes within an HR management context.
Practical examples include:
- Fetching leave details to display in a dashboard.
- Validating leave status before approving or rejecting requests.
- Integrating leave data into payroll or attendance systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the leave record to retrieve. This is required to specify which leave entry to fetch. |
Output
The node outputs JSON data representing the leave record corresponding to the provided ID. The structure typically includes fields such as leave type, start and end dates, status, employee details, and any other metadata related to the leave request.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the leave, but this is not evident from the provided code.
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 credential in n8n is necessary to authorize requests.
Troubleshooting
- Missing or invalid ID: Since the ID property is required, omitting it or providing an incorrect value will likely cause errors or empty responses. Ensure the ID corresponds to an existing leave record.
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly set up in n8n credentials.
- API connectivity issues: Network problems or changes in the API endpoint may cause failures. Confirm the base URL is reachable and correct.
- Unexpected response format: If the API changes its response schema, the node's output might not match expectations. Check for updates or changes in the Cloodo HRM API documentation.
Links and References
- Cloodo HRM API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n Documentation on Creating Custom Nodes