WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node interacts with the WibiClick API to manage various resources, including employees. Specifically, for the Employee resource and the Update Employee Leave operation, it updates an employee's leave status within a specified website context. This is useful in scenarios where you need to programmatically mark an employee as on leave or not, and specify the start and end dates of their leave period.

Practical examples include:

  • Automatically updating employee leave status based on HR system triggers.
  • Integrating leave management into broader workflows such as payroll or scheduling.
  • Syncing leave data from external systems into WibiClick.

Properties

Name Meaning
Website ID The unique identifier of the website under which the employee record exists.
Employee ID The unique identifier of the employee whose leave status is being updated.
Is On Leave Boolean flag indicating whether the employee is currently on leave (true or false).
Leave Start Date The starting date and time of the employee's leave period (ISO 8601 datetime format).
Leave End Date The ending date and time of the employee's leave period (ISO 8601 datetime format).

Output

The output JSON object contains the response from the WibiClick API after attempting to update the employee's leave status. It typically includes confirmation details about the update operation, such as success status and possibly the updated employee leave information.

Example output structure:

{
  "employeeId": "string",
  "isOnLeave": true,
  "leaveStartDate": "2024-06-01T00:00:00Z",
  "leaveEndDate": "2024-06-10T23:59:59Z",
  "message": "Leave status updated successfully"
}

(Note: The exact fields depend on the API response but generally confirm the update.)

Dependencies

  • Requires an active connection to the WibiClick API.
  • Requires an API key credential configured in n8n for authentication.
  • The node uses HTTP requests to communicate with the WibiClick API endpoints.
  • Proper permissions on the API key to update employee leave data are necessary.

Troubleshooting

  • Invalid or missing Website ID or Employee ID: Ensure these IDs are correct and correspond to existing records in WibiClick.
  • Authentication errors: Verify that the API key credential is valid and has the required permissions.
  • Date format issues: Leave start and end dates must be valid ISO 8601 datetime strings; invalid formats will cause errors.
  • API errors: If the API returns an error, check the message for details. Common issues include trying to update a non-existent employee or providing inconsistent leave dates (e.g., start date after end date).
  • Network issues: Ensure that the n8n instance can reach the WibiClick API endpoint.

Links and References

Discussion