WibiClickInstall

Overview

The node integrates with the WibiClick API to perform various operations across multiple resources such as jobs, contacts, employees, invoices, and more. Specifically for the Job resource and the Check Technician Availability operation, the node checks whether a particular employee (technician) is available on a specified website.

This operation is useful in scenarios where you need to verify technician availability before scheduling jobs or assigning tasks, helping to avoid conflicts and optimize workforce management.

Example use case:
Before creating a new job assignment, you can use this node to check if the selected technician is free during the desired time slot, ensuring efficient scheduling and reducing double bookings.

Properties

These properties are required inputs for the "Check Technician Availability" operation under the "Job" resource.

Output

The output JSON contains the response from the WibiClick API regarding the technician's availability status. The exact structure depends on the API but typically includes fields indicating whether the technician is available or not, along with any relevant details.

Example output structure (illustrative):

{
  "available": true,
  "employeeId": "employee-id-string",
  "websiteId": "website-id-string",
  "details": {
    "nextAvailableSlot": "2024-06-15T09:00:00Z",
    "conflicts": []
  }
}

No binary data output is involved in this operation.

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.
• Proper permissions and valid IDs for Website and Employee must be provided.

Troubleshooting

• Common issues:

  • Missing or invalid Website ID or Employee ID parameters will cause errors.
  • Network connectivity problems or incorrect API credentials will result in authentication failures.
  • If the API returns unexpected responses, it may indicate issues with the WibiClick service or incorrect parameter usage.

• Error messages:

  • "Failed to create note" — unrelated to this operation but indicates failure in note creation.
  • "Either contactId or phoneNumber is required" — unrelated here but shows parameter validation pattern.
  • For this operation, typical errors would come from HTTP request failures or API error responses, surfaced as node errors.

• Resolution tips:

  • Verify that the Website ID and Employee ID are correct and exist in the WibiClick system.
  • Ensure the API key credential is correctly set up and has necessary permissions.
  • Check network access and endpoint URLs.
  • Review API documentation for any changes or additional required parameters.

Links and References

• WibiClick API Documentation (Assumed URL; replace with actual if known)
• n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
• General n8n Credential Setup Guide: https://docs.n8n.io/credentials/

Note: This summary is based solely on static analysis of the provided source code and input property definitions. Runtime behavior and dynamic API responses are not executed or tested here.