Actions37
- Message Actions
- Media Actions
- Contact Actions
- Group Actions
- Instance Actions
- Webhook Actions
Overview
This node provides integration with the Uazapi WhatsApp API, enabling users to manage WhatsApp messaging and instance settings programmatically within n8n workflows. Specifically, the Instance - Logout operation logs out the current WhatsApp instance from the Uazapi service.
Typical use cases include:
- Automating the logout process of a WhatsApp instance when it is no longer needed or before switching accounts.
- Managing WhatsApp session lifecycle as part of broader automation workflows.
- Ensuring security by programmatically terminating active WhatsApp sessions.
Example: Automatically log out a WhatsApp instance at the end of a business day to prevent unauthorized access outside working hours.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra parameters for the logout request. Options include: |
| - Reply to Message ID: ID of message to reply to (string) | |
| - Delay (seconds): Delay before sending message (number) | |
| - Disable Link Preview: Disable link previews in messages (boolean) | |
| - Mention Users: Phone numbers to mention, comma-separated (string) |
Note: For the Instance - Logout operation, these additional fields may not have direct effect but are available as part of the generic "Additional Fields" collection.
Output
The node outputs a JSON object containing the response from the Uazapi API after attempting to log out the WhatsApp instance. The structure typically includes status information about the logout operation.
Example output JSON structure:
{
"status": "success",
"message": "Instance logged out successfully"
}
If an error occurs, the output will contain an error field with the error message.
No binary data is produced by this operation.
Dependencies
Requires an active Uazapi API credential with:
- API key
- API token
- API base URL
- Instance ID
The node sends requests through a proxy endpoint hosted at
https://n8ntools.io/api/v1/proxy/uazapi.Proper configuration of the Uazapi credentials in n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or expired API token or API key leading to authorization errors.
- Incorrect instance ID causing failure to identify the WhatsApp instance.
- Network connectivity problems preventing communication with the Uazapi proxy.
Error messages:
"Unauthorized"or"Invalid API key/token": Verify that the API credentials are correct and have not expired."Instance not found": Check that the instance ID is valid and corresponds to an active WhatsApp instance.- Timeout or network errors: Ensure n8n server has internet access and can reach the proxy URL.
Resolution tips:
- Re-enter or refresh API credentials in n8n.
- Confirm instance ID from the Uazapi dashboard or API.
- Test connectivity to the proxy URL outside n8n to rule out network issues.
Links and References
- Uazapi Official Documentation (generic placeholder, replace with actual if available)
- n8n Documentation on Credentials
- WhatsApp Business API Concepts
This summary focuses exclusively on the Instance - Logout operation of the Uazapi node based on static code analysis and provided property definitions.