UazapiGo Unofficial icon

UazapiGo Unofficial

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

Actions18

Overview

This node integrates with the uazapiGO API, enabling management of WhatsApp instances and sending messages through them. It supports administrative tasks such as creating and listing instances, updating instance metadata, configuring global webhooks, and managing privacy settings. Additionally, it allows sending text and media messages, handling profile updates, and webhook configurations.

The "Ver Webhook Global" operation under the "Administração" (Administration) resource specifically retrieves the current global webhook configuration that receives events from all WhatsApp instances managed by the system.

Practical example:
If you want to monitor all events across your WhatsApp instances centrally, you can use this operation to fetch the existing global webhook URL and event subscriptions. This helps in auditing or debugging webhook setups without manually checking each instance.

Properties

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

Output

The output is a JSON object representing the response from the uazapiGO API for the global webhook configuration request. Typically, this includes details such as:

  • The global webhook URL currently set.
  • The list of events subscribed to on the global webhook.

Example output structure (simplified):

{
  "url": "https://your-webhook-url.com",
  "events": [
    "connection",
    "messages",
    "contacts"
  ]
}

No binary data is produced by this operation.

Dependencies

  • Requires an admin-level API authentication token credential to access administrative endpoints.
  • The node expects the admin token to be configured in the node credentials before executing admin operations.
  • The base API URL can be customized but defaults to https://api.uazapigo.com.

Troubleshooting

  • Missing Admin Credentials Error:
    If the node throws an error indicating that admin credentials are not found, ensure that the required API key or token with administrative privileges is properly configured in the node's credentials section.

  • Invalid URL or Network Issues:
    If the request to the API fails, verify that the base URL is correct and reachable from your n8n environment. Also, check network connectivity and firewall rules.

  • Unexpected API Response:
    If the output does not contain expected webhook information, confirm that the global webhook has been configured previously via the API or UI.

Links and References

Discussion