WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node integrates with the WibiClick API to manage various business resources such as notes, jobs, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, users, technicians, tasks, suppliers, and settings. Specifically for the Estimate resource with the Get Estimate Number operation, the node retrieves the next available estimate number for a specified website.

This functionality is useful in scenarios where you need to generate or display the next sequential estimate number before creating a new estimate, ensuring consistent numbering and avoiding duplicates.

Practical example:
Before creating a new estimate for a client on a particular website, you can use this node operation to fetch the next estimate number to assign it explicitly or display it in your workflow or UI.

Properties

Name Meaning
Website ID The unique identifier of the website for which to retrieve the next estimate number.

Output

The output JSON contains the response from the WibiClick API endpoint that provides the next estimate number for the given website. The exact structure depends on the API but typically includes fields like the next estimate number or related metadata.

Example output JSON (structure may vary):

{
  "estimateNumber": 113
}

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the WibiClick API.
  • Requires an API key credential for authentication with the WibiClick service.
  • The node uses HTTP requests to communicate with the API endpoints.
  • The websiteId parameter must be provided to specify the context for the estimate number retrieval.

Troubleshooting

  • Missing or invalid Website ID: The operation requires a valid website ID. Ensure the Website ID property is correctly set.
  • Authentication errors: If the API key is missing, invalid, or expired, the node will fail to authenticate. Verify the API key credential configuration.
  • API connectivity issues: Network problems or incorrect API URL configurations can cause request failures.
  • Unexpected API responses: If the API returns unexpected data or errors, check the API documentation and ensure the website ID exists and is accessible.
  • Error handling: If the node is configured to continue on failure, errors will be returned in the output JSON with success set to false and an error message.

Links and References

Discussion