Overview
The node interacts with the Cloodo HRM system, specifically to retrieve multiple leave records when using the "Leave" resource with the "Get many" operation. It allows users to fetch paginated lists of leave entries, optionally filtered and sorted by various criteria such as search terms and date ranges.
This node is beneficial in scenarios where you need to automate HR workflows, generate reports on employee leaves, or synchronize leave data with other systems. For example, a user might want to pull all leave requests submitted within a specific date range or search for leaves matching certain keywords.
Properties
| Name | Meaning |
|---|---|
| Page | The page number or cursor for paginated results to specify which subset of leave records to retrieve. |
| Additional Fields | A collection of optional filters and sorting options: |
| - Search | A string to filter leave records by a search term. |
| - Sort | The order to sort results, either "desc" (descending) or "asc" (ascending). |
| - From Date | Start date to filter leave records from (inclusive). |
| - To Date | End date to filter leave records up to (inclusive). |
Output
The output contains a JSON array of leave records matching the query parameters. Each record typically includes details about individual leave entries such as employee information, leave type, dates, status, and other relevant metadata.
If the node supports binary data output (not evident from the provided code), it would represent attachments or documents related to leave requests, but this is not indicated 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 responses and sends requests with appropriate headers (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Empty or missing results: Ensure that the pagination parameter ("Page") is correctly set and that any filters like date ranges or search terms are valid and match existing data.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Invalid date formats: The "From Date" and "To Date" fields should be in a format accepted by the API (usually ISO 8601). Incorrect formats may cause request failures.
- Sorting issues: Only "asc" or "desc" are valid values for the "Sort" field; other inputs may lead to errors or unexpected ordering.
Links and References
- Cloodo HRM API Documentation (Assumed based on base URL; verify actual docs)
- n8n documentation on HTTP Request Node for understanding API interactions in custom nodes