WibiClickInstall

Overview

The node interacts with the WibiClick API to manage various 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 and the Update Estimate Status operation, the node updates the status or reason of an existing estimate.

This operation is useful in workflows where you need to programmatically change the status of an estimate, for example, marking it as approved, rejected, or pending based on external triggers or business logic. Practical examples include automating follow-ups after customer review or integrating estimate status changes with other systems like CRM or accounting software.

Properties

Output

The output JSON contains the response from the WibiClick API after attempting to update the estimate status. This typically includes confirmation of the update and any relevant data about the updated estimate. The exact structure depends on the API response but generally confirms success or failure and may include updated estimate details.

Example output snippet:

{
  "json": {
    "success": true,
    "estimate": {
      "id": "estimate-id",
      "status": "new-status",
      "reason": "updated reason"
      // ... other estimate fields
    }
  }
}

No binary data output is involved in this operation.

Dependencies

• Requires a valid API key credential for authenticating with the WibiClick API.
• The node makes HTTP POST requests to the endpoint /update-estimate-status of the WibiClick API.
• The API URL and key must be configured in the node credentials.

Troubleshooting

• Common issues:

  • Missing or invalid Website ID or Estimate ID will cause the API request to fail.
  • Providing an invalid or unsupported reason/status string might result in an error or no update.
  • Network or authentication errors if the API key is incorrect or expired.

• Error messages:

  • If the API returns an error, it will be thrown as a node error with the message from the API.
  • If the update fails without a clear message, the node throws a generic error indicating failure to update the estimate status.

• Resolution tips:

  • Verify that the Website ID and Estimate ID are correct and exist in the system.
  • Ensure the reason/status value matches expected values supported by the API.
  • Confirm the API key credential is valid and has necessary permissions.
  • Check network connectivity and API availability.

Links and References

• WibiClick API Documentation (Assumed, replace with actual link if available)
• n8n documentation on HTTP Request Node for understanding how API calls are made.
• General best practices for managing API keys and credentials in n8n workflows.