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
The node interacts with the WibiClick API to manage estimates and other related resources. Specifically, for the Estimate resource with the Get Estimates operation, it retrieves multiple estimate records associated with a specified website. This is useful in scenarios where you want to fetch a list of estimates for reporting, analysis, or further processing within an automation workflow.
Practical examples include:
- Fetching all estimates for a particular website to generate a summary report.
- Retrieving estimates filtered by employee, customer, or job IDs to analyze performance or workload.
- Paginating through large sets of estimates using limit and offset parameters.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website for which to retrieve estimates. |
| Limit | Maximum number of estimate results to return (pagination control). |
| Offset | Number of estimate records to skip before starting to collect the result set (pagination). |
| Additional Fields | Optional filters to narrow down estimates by: |
| - Employee ID: Filter estimates created by a specific employee. | |
| - Customer ID: Filter estimates related to a specific customer. | |
| - Job ID: Filter estimates associated with a specific job. |
Output
The output JSON contains the data returned from the WibiClick API endpoint /estimates. It typically includes an array or collection of estimate objects matching the query parameters.
Each estimate object may contain fields such as:
- Estimate ID
- Customer ID
- Employee ID
- Job ID
- Estimate details like name, notes, number, issued date, due date, sales amount, and line items.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the WibiClick API.
- Requires an API key credential configured in n8n for authentication.
- The API base URL and key are retrieved from the node credentials.
- The node uses HTTP GET requests with query string parameters to fetch estimates.
Troubleshooting
- Invalid or missing Website ID: The API requires a valid website ID; ensure this is correctly provided.
- API Authentication Errors: If the API key is invalid or missing, requests will fail. Verify the API key credential configuration.
- Pagination Issues: If too many results are requested without proper pagination (limit/offset), the API might reject the request or return incomplete data.
- Filter Parameters: Providing invalid employeeId, customerId, or jobId filters may result in empty responses.
- Network or API Downtime: Network issues or WibiClick API downtime can cause request failures; check connectivity and API status.
Common error messages usually come from the API response and are surfaced by the node. They should be addressed by verifying input parameters and credentials.
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 Credentials Setup: https://docs.n8n.io/nodes/credentials/overview/
This summary focuses on the "Estimate" resource and the "Get Estimates" operation as requested, based solely on static code analysis of the provided source and property definitions.