UazapiGo Unofficial icon

UazapiGo Unofficial

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

Overview

This node integrates with the unofficial uazapiGO API to manage WhatsApp instances and send messages. It supports various operations such as connecting or disconnecting an instance, checking its status, updating instance names, managing privacy settings, handling webhooks, and sending text or media messages.

The "Verificar status da instância" (Check instance status) operation specifically retrieves the current status of a given WhatsApp instance. This is useful for monitoring whether the instance is connected, disconnected, or in another state, enabling workflows that depend on the availability or health of the WhatsApp connection.

Practical example:

  • Automatically check the status of a WhatsApp instance before attempting to send messages, ensuring messages are only sent when the instance is active.
  • Monitor multiple instances' statuses periodically to trigger alerts or maintenance tasks if any instance goes offline.

Properties

Name Meaning
Url Base URL of the uazapiGO API. Default: https://api.uazapigo.com.
Token da Instância Authentication token for the specific WhatsApp instance. Not a credential but required for API calls related to instance, profile, webhook, and sending messages.

Output

The output is a JSON object representing the response from the uazapiGO API for the requested operation. For the "Verificar status da instância" operation, this JSON contains the current status details of the specified WhatsApp instance, such as connection state and other relevant metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the uazapiGO API endpoint, typically at https://api.uazapigo.com.
  • The node expects a valid instance authentication token (Token da Instância) to authorize requests.
  • Optionally, for administrative operations, an admin API token credential may be required (not applicable for this operation).
  • No additional external libraries beyond standard HTTP request helpers provided by n8n.

Troubleshooting

  • Missing or invalid token: If the instance token is missing or incorrect, the API will reject the request. Ensure the token is correctly set in the node parameters.
  • Incorrect URL format: The base URL should be a valid HTTPS URL without protocol duplication. The node sanitizes this, but verify the input if errors occur.
  • API connectivity issues: Network problems or API downtime can cause request failures. Check network access and API service status.
  • Error responses from API: The node throws errors if the API returns error messages. Review the error message for clues, such as invalid parameters or unauthorized access.
  • Continue On Fail: 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 details about other operations or resources, feel free to ask!

Discussion