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 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 or media messages to contacts or groups.

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

Common scenarios:

  • Monitoring all WhatsApp instances centrally by fetching the global webhook configuration.
  • Automating administrative workflows like creating new WhatsApp instances or updating their metadata.
  • Sending notifications or media messages programmatically via WhatsApp.
  • Configuring webhooks to receive real-time event updates from WhatsApp instances.

Practical example:
A user wants to verify which URL is currently set to receive global webhook events for all WhatsApp instances. Using this node with the "Administração" resource and "Ver Webhook Global" operation, they can fetch and inspect the webhook URL and subscribed events to ensure correct setup.

Properties

Name Meaning
Url Base URL of the uazapiGO API. Default is https://api.uazapigo.com. This can be customized if needed.
Token da Instância Authentication token for a specific WhatsApp instance. Required for most operations except admin-level ones.
Categoria (Resource) The category of operation: Administração (admin), Instancia (instance), Perfil (profile), Webhooks e SSE (webhook), Enviar Mensagem (sendMessage).
Operação (Operation) The specific action to perform within the selected resource. For Administração, options include: Criar Instancia, Listar todas as instâncias, Atualizar campos administrativos, Ver Webhook Global, Configurar Webhook Global.
Nome da Instância Name for a new WhatsApp instance (used in createInstance).
Nome do Sistema Optional system name when creating an instance.
ID da Instancia Instance ID to update administrative fields.
Campo Administrador 1 & 2 Custom metadata fields for administrative purposes.
URL do Webhook URL to receive webhook events (used in setting global or instance webhooks).
Eventos List of event types to monitor on the webhook (e.g., connection, messages, calls).

For the "Ver Webhook Global" operation specifically, only the Url property is required as input.

Output

The output JSON contains the response from the uazapiGO API endpoint /globalwebhook and includes the current global webhook configuration:

  • url: The URL configured to receive global webhook events.
  • events: An array of event names that are subscribed to on the global webhook.

Example output JSON structure:

{
  "url": "https://example.com/global-webhook",
  "events": [
    "connection",
    "messages",
    "calls"
  ]
}

This output allows users to programmatically check which webhook URL is active globally and what events it listens to.

Dependencies

  • Requires access to the uazapiGO API, typically via an internet connection.
  • For admin-level operations (including "Ver Webhook Global"), an API key credential with admin privileges must be configured in n8n and linked to the node.
  • The base API URL defaults to https://api.uazapigo.com but can be overridden.
  • No other external dependencies are required.

Troubleshooting

  • Missing Admin Credentials Error:
    If the node throws an error about missing admin credentials, ensure that an appropriate API key credential with admin rights is configured and connected to the node.

  • Invalid or Missing Token:
    For non-admin operations, a valid instance token must be provided. Failure to supply this will result in authentication errors.

  • Incorrect URL Format:
    The node sanitizes URLs by removing protocol prefixes before appending https://. Ensure the URL input is correct and reachable.

  • API Request Failures:
    Network issues or incorrect parameters may cause HTTP request failures. Check connectivity and parameter correctness.

  • Continue On Fail Behavior:
    If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

If you need further details on other operations or resources, feel free to ask!

Discussion