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 "Administração" resource and the "Atualizar campos administrativos" operation, it updates custom administrative metadata fields (adminField01 and adminField02) of a specified WhatsApp instance.

Common scenarios where this node is useful include:

  • Updating metadata or custom tags associated with WhatsApp instances for organizational or tracking purposes.
  • Managing administrative data without needing to directly access the backend system.
  • Automating updates to instance information as part of larger workflows.

For example, you might use this node to update internal notes or status flags on a WhatsApp instance after certain events occur in your workflow.

Properties

Name Meaning
Url Base URL of the uazapiGO API (e.g., https://api.uazapigo.com).
ID da Instancia The unique identifier of the WhatsApp instance whose admin fields will be updated.
Campo Administrador 1 Custom administrative field 1 for storing metadata related to the instance.
Campo Administrador 2 Custom administrative field 2 for storing additional metadata related to the instance.

Output

The node outputs an array of JSON objects representing the response from the uazapiGO API after attempting to update the administrative fields. The structure depends on the API response but generally includes confirmation of the update or error details.

No binary data output is produced by this operation.

Example output JSON snippet:

{
  "success": true,
  "updatedInstanceId": "instance-id-value",
  "adminField01": "new value",
  "adminField02": "new value"
}

Dependencies

  • Requires access to the uazapiGO API endpoint.
  • Requires an API token with administrative privileges (provided via credentials).
  • The node expects the admin token credential to be configured in n8n for authentication when using the "admin" resource operations.

Troubleshooting

  • Missing Admin Credentials: If the node throws an error about missing admin credentials, ensure that the required API key/token with admin rights is properly set up in n8n credentials.
  • Invalid Instance ID: Providing an incorrect or non-existent instance ID will cause the API to fail updating fields. Verify the instance ID before running the node.
  • Empty Fields: If adminField01 or adminField02 are empty strings or null, those fields will be omitted from the update request. Ensure values are provided if updates are intended.
  • API URL Issues: The base URL must be correctly formatted; the node normalizes it by removing any protocol prefix and re-adding https://. Make sure the URL is reachable and correct.
  • HTTP Errors: Network issues or invalid tokens can cause HTTP errors. Check connectivity and token validity.

Links and References

Discussion