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 perform various operations across multiple resources such as technicians, jobs, contacts, employees, invoices, and more. Specifically for the Technician resource and the Get Monthly Report Text operation, the node fetches a textual monthly report for a given technician based on the specified year and month.
This functionality is useful in scenarios where you want to retrieve summarized or detailed monthly performance or activity reports of technicians in text format, which can be used for review, payroll processing, or reporting purposes.
Example use case:
A service company wants to automatically generate monthly performance summaries for their field technicians and send these reports via email or store them in a database for further analysis.
Properties
| Name | Meaning |
|---|---|
| Technician ID | The unique identifier of the technician for whom the monthly report text is requested. |
| Year | The year for which the monthly report is generated (e.g., 2024). |
| Month | The month (1-12) for which the monthly report is generated. |
Output
The output JSON contains a single field:
textReport: A string containing the technician's monthly report in text format for the specified year and month.
Example output:
{
"textReport": "Technician John Doe completed 15 jobs in March 2024 with an average customer satisfaction rating of 4.8."
}
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 API.
- The node uses HTTP requests to communicate with the API endpoints.
Troubleshooting
- Invalid Technician ID: If the technician ID does not exist or is incorrect, the API may return an error or empty response. Verify the technician ID before running the node.
- Invalid Date Parameters: Ensure that the year and month are valid numbers and represent a real calendar month (month between 1 and 12).
- API Authentication Errors: If the API key is missing, invalid, or expired, the node will fail to authenticate. Check the API key credentials configured in n8n.
- Network Issues: Connectivity problems with the WibiClick API endpoint can cause request failures. Verify network access and API availability.
- Unexpected API Response: If the API returns unexpected data or errors, check the API documentation or contact support.
Links and References
- WibiClick API Documentation (Assumed URL, replace with actual if available)
- n8n Documentation: Creating Custom Nodes
- General API Integration Best Practices
If you need details about other operations or resources, feel free to ask!