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 send messages. It supports multiple resources such as instance management, profile updates, webhook configuration, and message sending.

Specifically, for the "Instancia" resource and the "Verificar status da instância" operation, the node queries the current status of a specific WhatsApp instance. This is useful for monitoring whether an instance is connected, disconnected, or in another state, enabling automation workflows that depend on the instance's availability or health.

Practical example:
You can use this node to periodically check if your WhatsApp instance is online before attempting to send messages, ensuring your workflow only proceeds when the instance is ready.

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).

Output

The output is a JSON object representing the response from the uazapiGO API about the instance status. The exact structure depends on the API but typically includes fields indicating connection status, session details, and other metadata about the WhatsApp instance.

No binary data is output by this operation.

Example output snippet (conceptual):

{
  "status": "connected",
  "instanceId": "abc123",
  "qrCode": null,
  "phoneNumber": "+5511999999999",
  "lastSeen": "2024-06-01T12:00:00Z"
}

Dependencies

  • Requires access to the uazapiGO API endpoint.
  • Needs a valid instance authentication token provided as an input property.
  • No special n8n credentials are mandatory for this operation, but an API key credential may be used for admin operations (not relevant here).

Troubleshooting

  • Common issues:

    • Missing or invalid instance token will cause authentication errors.
    • Incorrect base URL may lead to connection failures.
    • Network issues or API downtime can cause request timeouts or errors.

  • Error messages:

    • "Credenciais de Admin não encontradas." — This error is related to admin operations and should not occur for this instance status check.
    • HTTP errors from the API (e.g., 401 Unauthorized) indicate token problems; verify the token value.
    • If the node throws a network error, check the URL and internet connectivity.

  • Resolution tips:

    • Ensure the token is correctly set and corresponds to the target instance.
    • Confirm the base URL is reachable and correct.
    • Use the "Continue On Fail" option in n8n to handle intermittent API errors gracefully.

Links and References

Discussion