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 configure webhooks for event monitoring. Specifically, the "Configurar Webhook da Instância" operation under the "Webhooks e SSE" resource allows users to set up a webhook URL that will receive events related to a specific WhatsApp instance. This is useful for real-time event handling such as message reception, connection status changes, or other WhatsApp-related activities.

Practical scenarios include:

  • Automatically processing incoming WhatsApp messages by receiving webhook callbacks.
  • Monitoring connection or presence events of a WhatsApp instance.
  • Integrating WhatsApp events into other systems or workflows via webhook notifications.

Properties

Name Meaning
Url Base URL of the uazapiGO API (e.g., https://api.uazapigo.com).
Token da Instância Authentication token for the specific WhatsApp instance (not a credential).
URL do Webhook The URL endpoint where webhook events will be sent.
Eventos List of event types to monitor and receive via webhook. Options include: Connection, History, Messages, Messages Update, Call, Contacts, Presence, Groups, Labels, Chats, Chat Labels, Blocks, Leads, Sender.

Output

The node outputs JSON data representing the response from the uazapiGO API after configuring the webhook. The structure depends on the API's response but generally includes confirmation of the webhook URL and the list of subscribed events.

No binary data output is produced by this operation.

Example output JSON snippet:

{
  "url": "https://meusite.com/webhook",
  "events": ["messages", "connection", "presence"],
  "status": "success"
}

Dependencies

  • Requires access to the uazapiGO API endpoint specified by the "Url" property.
  • Requires an authentication token for the WhatsApp instance ("Token da Instância").
  • No internal n8n credentials are mandatory for this operation, but an API key credential may be used for admin operations.
  • Proper network connectivity to the webhook URL to receive events.

Troubleshooting

  • Common issues:

    • Invalid or missing instance token: The API will reject requests without proper authentication.
    • Incorrect webhook URL format: The URL must be a valid HTTPS URL; otherwise, the API may return an error.
    • Network issues preventing webhook delivery: Ensure the webhook URL is publicly accessible and can accept POST requests.
    • Selecting no events: If no events are selected, the webhook might not trigger any callbacks.

  • Error messages:

    • "Credenciais de Admin não encontradas." — Occurs if admin credentials are required but not provided. For this operation, ensure the instance token is set.
    • HTTP errors from the API (e.g., 400 Bad Request) usually indicate invalid parameters like malformed URLs or missing required fields.

  • Resolution tips:

    • Double-check the token and URL inputs.
    • Verify the webhook endpoint is reachable and correctly configured to handle incoming POST requests.
    • Select at least one event to monitor.

Links and References

Discussion