Overview
The node "Cloodo HRM" integrates with the Cloodo HRM system via its API, allowing users to perform various operations related to employee and leave management. Specifically, for the Employee resource and the GET Client operation, the node retrieves client information associated with a particular employee account. This is useful in scenarios where you need to fetch client data linked to employees, such as generating reports, managing client assignments, or syncing client details with other systems.
Practical examples:
- Fetching all clients managed by a specific employee to display in a dashboard.
- Retrieving client lists for an employee before performing bulk updates or notifications.
- Integrating client data into CRM or project management tools based on employee assignments.
Properties
| Name | Meaning |
|---|---|
| Employee Account | The unique identifier (account) of the employee whose clients you want to retrieve. |
| Page | Pagination parameter to specify which page of results to fetch when retrieving clients. |
Output
The node outputs JSON data containing the list of clients associated with the specified employee account. The structure typically includes client details such as client IDs, names, contact information, and any other metadata provided by the Cloodo HRM API for clients.
If pagination is used, the output may also include metadata about the current page, total pages, or cursors for fetching subsequent pages.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Cloodo HRM API endpoint at
https://erp-amz.cloodo.com/v4. - An API authentication token or key credential must be configured in n8n to authorize requests.
- The node depends on the external Cloodo HRM service being available and responsive.
Troubleshooting
- Missing or invalid employee account: If the
employee_idproperty is empty or incorrect, the API call will fail or return no clients. Ensure the employee account ID is valid and correctly entered. - Pagination issues: Providing an invalid
pagevalue might result in empty responses or errors. Use valid page numbers or omit the field to get default results. - Authentication errors: If the API key or token is missing or expired, the node will throw authorization errors. Verify that credentials are properly set up in n8n.
- API downtime or network issues: Temporary unavailability of the Cloodo HRM API can cause request failures. Retry after some time or check network connectivity.
Links and References
- Cloodo HRM API Documentation (assumed URL based on baseURL)
- n8n documentation on HTTP Request Node for understanding API integrations
- General guidance on pagination handling in n8n nodes