WibiClickInstall

Overview

This 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 Note resource with the Delete operation, it deletes a note identified by its Note ID.

Common scenarios where this node is beneficial include automating the management of notes within a website or application context, such as removing outdated or irrelevant notes programmatically. For example, you might use this node in a workflow that cleans up notes after a certain period or when a related entity (like a job or contact) is deleted.

Properties

Output

The output JSON object contains the response from the WibiClick API after attempting to delete the note. It typically includes information about the success or failure of the deletion request. The exact structure depends on the API's response but generally confirms whether the note was successfully deleted.

Example output:

{
  "success": true,
  "message": "Note deleted successfully"
}

or an error message if deletion failed.

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 service.
• The node uses HTTP requests to communicate with the WibiClick API endpoints.
• Proper configuration of the API URL and API key in the node credentials is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing Note ID or Website ID parameters will cause the deletion to fail.
  • Authentication errors if the API key is invalid or missing.
  • Network connectivity issues preventing access to the WibiClick API.
  • Attempting to delete a note that does not exist may result in an error response.

• Error messages:

  • "Failed to delete note" or similar indicates the API did not confirm deletion; verify IDs and permissions.
  • HTTP 401 Unauthorized suggests issues with API key credentials.
  • HTTP 404 Not Found may indicate the note or website ID does not exist.

• Resolution tips:

  • Double-check that the Note ID and Website ID are correct and correspond to existing entities.
  • Ensure the API key credential is valid and has sufficient permissions.
  • Verify network connectivity and API endpoint accessibility.
  • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

• WibiClick API Documentation (Assumed URL, replace with actual if available)
• n8n Documentation on HTTP Request Node
• General n8n Node Development Guide