UazapiGo Unofficial icon

UazapiGo Unofficial

Interage com a API uazapiGO para gerenciar instâncias e enviar mensagens

Actions18

Overview

This node integrates with the unofficial uazapiGO API to manage WhatsApp instances and send messages. It supports administrative tasks such as creating and listing WhatsApp instances, updating instance metadata, configuring webhooks, managing privacy settings, and sending text or media messages.

The "Listar todas as instâncias" (List all instances) operation under the "Administração" (Administration) resource retrieves a complete list of all WhatsApp instances registered in the system. This is useful for administrators who need to monitor or audit all active instances centrally.

Practical example:
An administrator wants to get an overview of all WhatsApp instances currently managed by their system to check statuses or perform bulk updates. Using this node's list operation, they can fetch all instances and then process or display them in a dashboard.

Properties

Name Meaning
Url Base URL of the uazapiGO API. Default is https://api.uazapigo.com. This can be customized if needed.

Note: For the "Listar todas as instâncias" operation, only the "Url" property is required as input.

Output

The output is a JSON array where each item corresponds to an instance returned by the API. The exact structure depends on the API response but typically includes details about each WhatsApp instance such as its ID, name, status, and any associated metadata.

No binary data is output by this operation.

Example output snippet (conceptual):

[
  {
    "id": "instance1",
    "name": "My WhatsApp Instance",
    "status": "connected",
    "adminField01": "...",
    "adminField02": "..."
  },
  {
    "id": "instance2",
    "name": "Backup Instance",
    "status": "disconnected"
  }
]

Dependencies

  • Requires access to the uazapiGO API endpoint.
  • Requires an admin API token credential configured in n8n to authenticate administrative operations.
  • The base URL of the API can be customized via the "Url" property.
  • No other external dependencies are needed.

Troubleshooting

  • Missing Admin Credentials Error:
    If the node throws an error stating that admin credentials are not found, ensure that you have configured the required API key or token credential in n8n for administrative access.

  • API Connection Issues:
    Verify that the "Url" property points to a valid and reachable uazapiGO API endpoint. Network issues or incorrect URLs will cause request failures.

  • Empty or Unexpected Response:
    If the output is empty or does not contain expected instance data, confirm that there are instances registered in the system and that your admin token has sufficient permissions.

  • HTTP Errors:
    Common HTTP errors like 401 Unauthorized indicate authentication problems; 404 Not Found may indicate incorrect endpoints; 500 Internal Server Error suggests server-side issues.

Links and References

Discussion