WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node integrates with the WibiClick API to manage various resources such as users, websites, notes, jobs, contacts, employees, estimates, invoices, line items, WhatsApp messages, tasks, suppliers, settings, and technicians. Specifically for the User resource and the Disconnect User From Website operation, the node allows you to disconnect a user from a specified website by sending a request to the WibiClick API.

This operation is useful in scenarios where you want to revoke or remove a user's association with a particular website, for example, when a user no longer needs access or has left an organization.

Practical example:
You have a user who was previously connected to a website for managing content or analytics. When this user leaves your team, you can use this node operation to disconnect them from that website, ensuring they no longer have access or permissions related to it.

Properties

Name Meaning
Website ID The unique identifier of the website from which the user will be disconnected.
User ID The unique identifier of the user to disconnect from the specified website.

These properties are required inputs for the operation.

Output

The output JSON contains the response from the WibiClick API after attempting to disconnect the user from the website. Typically, it includes success status and any relevant data returned by the API indicating whether the disconnection was successful.

Example output structure:

{
  "success": true,
  "message": "User disconnected from website successfully"
}

(Note: The exact fields depend on the API response.)

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 POST requests to communicate with the API endpoint /disconnect-user-from-website.
  • No additional environment variables or external services are needed beyond the configured API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Website ID or User ID parameters will cause the API call to fail.
    • Authentication errors if the API key credential is invalid or expired.
    • Network connectivity issues preventing communication with the WibiClick API.

  • Error messages:

    • If the API returns an error, the node throws an error with the message from the API response.
    • If the node is set to continue on failure, it outputs a JSON object with success: false and the error message.
    • Typical error messages might include "User not found", "Website not found", or "Unauthorized".

  • Resolution tips:

    • Verify that the Website ID and User ID are correct and exist in the WibiClick system.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity and firewall settings.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion