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. Specifically, for the Instancia resource and the Buscar configurações de privacidade operation, it retrieves the current privacy settings of a specified WhatsApp instance.

Use cases include:

  • Checking what privacy configurations (such as who can see last seen, profile photo, status, etc.) are currently applied to a WhatsApp instance.
  • Auditing or monitoring privacy settings before making changes.
  • Automating workflows that depend on privacy configuration states.

Example: A user wants to verify if the "last seen" visibility is set to "contacts only" before sending a message or updating settings.

Properties

Name Meaning
Url Base URL of the uazapiGO API. Default is https://api.uazapigo.com.
Token da Instância Authentication token specific to the WhatsApp instance. Required to authorize API requests.

Output

The node outputs a JSON object representing the privacy settings of the WhatsApp instance. The structure corresponds to the API response from the /instance/privacy endpoint and typically includes keys for various privacy options such as:

  • groupadd: Who can add the user to groups.
  • last: Who can see the last seen timestamp.
  • status: Who can see status updates.
  • profile: Who can see the profile photo.
  • readreceipts: Read receipt settings.
  • online: Online status visibility.
  • calladd: Who can make calls.

Each key's value indicates the level of visibility, e.g., "all", "contacts", "none", etc.

No binary data output is produced by this operation.

Dependencies

  • Requires an authentication token for the specific WhatsApp instance (Token da Instância).
  • The node makes HTTP requests to the uazapiGO API at the configured base URL.
  • No additional external services or environment variables are required beyond the API token.

Troubleshooting

  • Missing or invalid token: If the token parameter is empty or incorrect, the API will reject the request. Ensure the correct instance token is provided.
  • Incorrect URL: The base URL must be valid and reachable. The default is https://api.uazapigo.com.
  • API errors: The node throws errors if the API returns failure responses. Check the error message for details.
  • Network issues: Connectivity problems may cause timeouts or failures.
  • Permission issues: The token must have sufficient permissions to access privacy settings.

To resolve errors:

  • Verify the token is correct and active.
  • Confirm the API URL is accessible.
  • Check network connectivity.
  • Review API documentation for permission requirements.

Links and References

Discussion