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

Typical use cases include:

  • Retrieving privacy configurations such as who can see your last seen, profile photo, status, read receipts, calls, group additions, and online status.
  • Auditing or monitoring privacy settings programmatically within an automation workflow.
  • Using the retrieved privacy data to conditionally adjust messaging or user interactions based on privacy preferences.

Example: An automation that checks the privacy settings of a WhatsApp instance before sending certain types of messages or notifications.

Properties

Name Meaning
Url Base URL of the uazapiGO API (default: 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 current privacy settings of the WhatsApp instance. The exact structure depends on the API response but typically includes keys corresponding to different privacy options such as:

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

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

No binary data is output by this operation.

Dependencies

  • Requires access to the uazapiGO API endpoint.
  • Needs a valid authentication token for the specific WhatsApp instance (Token da Instância).
  • No special n8n credentials are mandatory for this operation, but the token must be provided as a parameter.
  • The node uses standard HTTP requests with JSON payloads.

Troubleshooting

  • Missing or invalid token: If the token parameter is missing or incorrect, the API will likely reject the request with an authentication error. Ensure the token is correctly set.
  • Incorrect URL: The base URL must be correct and accessible. Verify network connectivity and URL correctness.
  • API errors: The node throws errors if the API returns failure responses. Check the error message for details.
  • Empty or malformed response: If the API changes or returns unexpected data, the output may not match expectations. Validate the API response format.
  • Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.

Links and References


If you need details about other operations or resources, feel free to ask!

Discussion