UazapiGo Unofficial icon

UazapiGo Unofficial

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

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.

A common use case is automating WhatsApp instance management within a workflow, for example:

  • Listing all WhatsApp instances in your system to monitor their status.
  • Creating new WhatsApp instances programmatically.
  • Sending customized text or media messages to contacts or groups.
  • Configuring global or instance-specific webhooks to receive event notifications.

Specifically, the "Administração" resource with the "Listar todas as instâncias" operation returns a complete list of all WhatsApp instances registered in the system.

Properties

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

For this specific Resource-Operation ("Administração" - "Listar todas as instâncias"), only the Url property is relevant.

Output

The node outputs an array of JSON objects representing the response from the uazapiGO API endpoint /instance/all. Each object corresponds to a WhatsApp instance with its details as returned by the API.

The exact structure depends on the API but typically includes instance identifiers, names, statuses, and possibly metadata fields.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the uazapiGO API at the specified base URL.
  • For "admin" resource operations, an admin API token credential must be configured in n8n (referred generically as an API key credential).
  • The node uses HTTP requests with JSON payloads and expects JSON responses.

Troubleshooting

  • Missing Admin Credentials: If the admin API token is not set up or invalid, the node will throw an error indicating that admin credentials were not found. Ensure you have configured the required API authentication token in n8n credentials.
  • Invalid URL: The base URL must be a valid HTTPS URL. Incorrect URLs or missing protocol may cause connection errors.
  • API Errors: The node forwards API error messages. Common issues include unauthorized access (invalid token), rate limiting, or malformed requests.
  • Empty Response: If no instances exist, the returned list may be empty.

To resolve errors:

  • Verify the admin API token credential is correctly configured.
  • Confirm the base URL is correct and reachable.
  • Check API documentation or logs for detailed error messages.

Links and References

Discussion