Actions92
- Contact Actions
- Employee Actions
- Estimate Actions
- Invoice Actions
- Job Actions
- Line Item Actions
- Note Actions
- Setting Actions
- Supplier Actions
- Task Actions
- Technician Actions
- User Actions
- Website Actions
- WhatsApp Actions
Overview
This node integrates with the WibiClick API to manage various resources related to business operations, including employees, jobs, contacts, invoices, and more. Specifically, for the Employee resource and the Get Employees on Leave operation, the node retrieves a list of all employees who are currently marked as on leave for a specified website.
This functionality is useful in scenarios where you need to monitor employee availability, plan workforce allocation, or automate notifications based on employee leave status. For example, a manager could use this node to automatically fetch employees on leave and adjust scheduling or notify relevant teams accordingly.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website for which to retrieve employees on leave. Required. |
Output
The output JSON contains the response from the WibiClick API endpoint that returns employees currently on leave for the specified website. The structure typically includes an array or list of employee objects with their details such as name, leave dates, and status.
Example output structure (simplified):
{
"employees": [
{
"id": "employee-id-1",
"firstName": "John",
"lastName": "Doe",
"isOnLeave": true,
"leaveStartDate": "2024-06-01T00:00:00Z",
"leaveEndDate": "2024-06-10T00:00:00Z",
"description": "Annual leave"
},
{
"id": "employee-id-2",
"firstName": "Jane",
"lastName": "Smith",
"isOnLeave": true,
"leaveStartDate": "2024-06-05T00:00:00Z",
"leaveEndDate": "2024-06-15T00:00:00Z",
"description": "Medical leave"
}
]
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API.
- Requires an API key credential for authentication with the WibiClick service.
- The node expects the
websiteIdparameter to specify the context for employee data retrieval.
Troubleshooting
- Invalid or missing Website ID: The API call will fail if the
websiteIdis not provided or invalid. Ensure the correct website ID is set. - Authentication errors: If the API key credential is incorrect or expired, requests will be unauthorized. Verify and update the API key as needed.
- API rate limits or downtime: Temporary failures may occur due to API limits or service outages. Retry after some time or check the WibiClick service status.
- Unexpected response format: If the API changes its response structure, the node might not parse results correctly. Check for updates or contact support.
Links and References
- WibiClick API Documentation (Assumed URL; replace with actual if available)
- n8n Documentation on HTTP Request Node for understanding underlying HTTP calls.
This summary focuses exclusively on the Employee - Get Employees on Leave operation as requested.