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, profiles, webhooks, and send messages. It allows users to perform administrative tasks such as creating and listing instances, updating instance details, managing privacy settings, configuring webhooks, and sending text or media messages through WhatsApp instances.

A common use case is automating WhatsApp communication workflows, for example:

  • Creating and connecting WhatsApp instances programmatically.
  • Monitoring events via webhooks configured per instance.
  • Sending customized text or media messages to contacts or groups.
  • Managing profile information like display name and image.

This node is beneficial for businesses or developers who want to integrate WhatsApp messaging capabilities into their automation pipelines without using official WhatsApp APIs directly.

Properties

Name Meaning
Url Base URL of the uazapiGO API (e.g., https://api.uazapigo.com).
Token da Instância Authentication token for a specific WhatsApp instance (not a credential).

Additional properties relevant to "Webhooks e SSE" resource and "Ver Webhook da Instância" operation:

  • No additional input properties are required specifically for this operation beyond the base URL and instance token.

Output

The node outputs an array of JSON objects representing the response from the uazapiGO API for the requested operation.

For the "Ver Webhook da Instância" operation, the output JSON contains the current webhook configuration of the specified WhatsApp instance, including details such as the webhook URL and subscribed events.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the uazapiGO API endpoint specified by the "Url" property.
  • Requires a valid authentication token for the specific WhatsApp instance ("Token da Instância").
  • Optionally uses an admin token credential for administrative operations (not applicable here).
  • The node uses HTTP requests with JSON payloads and expects JSON responses.

Troubleshooting

  • Missing or invalid token: If the instance token is missing or incorrect, the API will reject the request. Ensure the token is correctly provided in the node parameters.
  • Incorrect URL format: The base URL must be a valid HTTPS URL. The node normalizes it by removing any protocol prefix before prepending "https://". Verify the URL is correct and reachable.
  • API errors: The node throws errors if the API returns error responses. Check the error message for details and verify the API status and credentials.
  • Network issues: Connectivity problems to the API endpoint can cause failures. Confirm network access and firewall rules allow outbound HTTPS requests to the API URL.

Links and References

Discussion