Wuzapi Admin icon

Wuzapi Admin

Administrative operations for Wuzapi WhatsApp API

Actions3

Overview

This node, named "Wuzapi Admin," provides administrative operations for managing users in the Wuzapi WhatsApp API system. It allows you to create new users, delete existing users (either partially or fully), and list all users. The "Delete User Full" operation specifically deletes a user completely, including their database records, S3 storage data, and logs them out.

Common scenarios where this node is beneficial include:

  • Automating user lifecycle management in a WhatsApp API environment.
  • Cleaning up user data entirely when a user is no longer needed.
  • Integrating user administration into workflows that require dynamic user creation or deletion.

For example, you might use the "Delete User Full" operation to ensure that when a user leaves your service, all their associated data and sessions are removed securely.

Properties

Name Meaning
User ID ID of the user to delete. This is required for both "Delete User" and "Delete User Full" operations. Example: 4e4942c7dee1deef99ab8fd9f7350de5

Output

The node outputs JSON data representing the result of the performed operation:

  • For "Delete User Full," the output will typically be a confirmation response from the API indicating successful deletion of the user and their associated data.
  • If an error occurs, the output JSON will contain an error field with the error message.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Wuzapi Admin API.
  • The node expects the API base URL and an admin token to be provided via credentials.
  • HTTP requests are made to the Wuzapi Admin API endpoints to perform operations.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID: Ensure the User ID is correctly specified and exists in the system.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network or connectivity problems: Check that the API endpoint URL is reachable from n8n.

  • Error messages:

    • Errors returned from the API will appear in the output JSON under the error field.
    • If the node fails without continuing on fail enabled, it will throw the error and stop execution.

To resolve errors:

  • Double-check input parameters, especially the User ID.
  • Confirm API credentials and network access.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

Discussion