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 such as employees, jobs, contacts, invoices, and more. Specifically for the Employee resource with the Delete Employee operation, it allows users to delete an employee record from a specified website by providing the employee's ID and the website ID.
Common scenarios where this node is beneficial include automating employee management workflows, such as removing former employees from a system, syncing employee data between platforms, or cleaning up outdated records in bulk.
Practical example:
- Automatically delete an employee from your WibiClick system when they leave the company by triggering this node with their employee ID and associated website ID.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website where the employee exists. |
| Employee ID | The unique identifier of the employee to be deleted. |
Output
The output JSON contains the response from the WibiClick API after attempting to delete the employee. Typically, it will include success status and any relevant messages returned by the API indicating whether the deletion was successful.
Example output structure:
{
"json": {
"success": true,
"message": "Employee deleted successfully"
}
}
(Note: Actual keys depend on the API response.)
Dependencies
- Requires an active connection to the WibiClick API.
- Needs an API key credential configured in n8n for authentication.
- The node uses HTTP requests to communicate with the WibiClick API endpoints.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Employee ID or Website ID will result in failure to delete.
- Network connectivity issues can cause request failures.
- Missing or incorrect API credentials will prevent successful API calls.
Error messages:
- If the employee does not exist, the API may return an error indicating the employee was not found.
- Authentication errors if the API key is invalid or missing.
- Validation errors if required parameters are missing.
Resolution tips:
- Verify that the Employee ID and Website ID are correct and exist in the system.
- Ensure the API key credential is properly set up and has necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- WibiClick API Documentation (Assumed URL; replace with actual)
- n8n HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/