Actions18
- Administração Actions
- Instancia Actions
- Perfil Actions
- Webhooks e SSE Actions
- Enviar Mensagem Actions
Overview
This node integrates with the unofficial uazapiGO API to manage WhatsApp instances and send messages. It supports operations such as connecting or disconnecting WhatsApp instances, checking instance status, updating instance names, managing privacy settings, configuring webhooks, and sending text or media messages.
The "Desconectar instância" (Disconnect instance) operation specifically disconnects a WhatsApp instance, effectively ending its current session. This is useful when you want to remotely terminate the connection of a WhatsApp instance managed via uazapiGO, for example, to reset the session or stop message processing temporarily.
Practical example:
You have an active WhatsApp instance connected to your system but need to disconnect it due to maintenance or troubleshooting. Using this node's "Desconectar instância" operation, you can programmatically disconnect the instance without manual intervention.
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. Required for instance-related operations including disconnecting. |
Output
The node outputs JSON data representing the response from the uazapiGO API for the disconnect request. The structure depends on the API response but generally includes confirmation of the disconnection or error details if the operation failed.
No binary data output is produced by this operation.
Example output JSON snippet (conceptual):
{
"success": true,
"message": "Instance disconnected successfully"
}
Dependencies
- Requires access to the uazapiGO API endpoint.
- Needs a valid authentication token for the specific WhatsApp instance (
Token da Instância). - Optional admin credentials are not required for this operation.
- The node expects the base URL of the API, which defaults to
https://api.uazapigo.combut can be customized.
Troubleshooting
- Missing or invalid token: If the token parameter is missing or incorrect, the API will reject the request. Ensure the correct instance token is provided.
- Incorrect URL: If the base URL is wrong or unreachable, the HTTP request will fail. Verify network connectivity and URL correctness.
- API errors: The API might return errors if the instance is already disconnected or does not exist. Check the response message for details.
- Node errors: If the node throws credential-related errors, verify that the token is set properly in the node parameters and not confused with admin credentials.
Links and References
- uazapiGO Official API Documentation (hypothetical link, replace with actual if available)
- WhatsApp Business API concepts for instance management (general reference)