UazAPI icon

UazAPI

Integração completa com UazAPI - 90+ endpoints para automação WhatsApp

Actions37

Overview

This node integrates with the UazAPI service, which provides extensive WhatsApp automation capabilities through more than 90 endpoints. Specifically, for the Instance - Update Name operation, it allows users to update the name of an existing WhatsApp instance managed by UazAPI.

Typical use cases include:

  • Renaming a WhatsApp instance to better reflect its purpose or owner.
  • Managing multiple WhatsApp instances and keeping their names consistent or updated.
  • Automating instance management workflows where instance names need to be changed dynamically based on external triggers.

For example, if you have a WhatsApp instance named "support-bot" and want to rename it to "customer-service-bot", this node operation will send the new name to the UazAPI backend to update the instance accordingly.

Properties

Name Meaning
Instance Name The unique identifier (current name) of the WhatsApp instance to operate on.
New Name The new name to assign to the WhatsApp instance.

Output

The output is a JSON object representing the response from the UazAPI server after attempting to update the instance name. This typically includes status information about the update operation, such as success confirmation or error details.

Example output structure (simplified):

{
  "success": true,
  "message": "Instance name updated successfully",
  "data": {
    "oldName": "previous-instance-name",
    "newName": "updated-instance-name"
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the UazAPI service.
  • Needs valid API credentials configured in n8n to authenticate requests to UazAPI.
  • The base URL for the UazAPI endpoint must be set in the credentials.
  • The node uses HTTP POST requests to communicate with the UazAPI backend.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials can cause authentication failures.
    • Providing a non-existent or incorrect current instance name may result in errors or no changes.
    • Network connectivity problems can prevent communication with the UazAPI server.
    • Attempting to rename to a name already in use might cause conflicts.

  • Error messages and resolutions:

    • "Authentication failed": Verify that the API key or token is correctly configured in n8n credentials.
    • "Instance not found": Check that the provided current instance name exists and is spelled correctly.
    • "Name already taken": Choose a different new name that is unique among your instances.
    • Timeout or network errors: Ensure stable internet connection and that the UazAPI service is reachable.

Links and References

Discussion