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 to another instance.
- Managing WhatsApp session lifecycle as part of broader automation workflows.
- Ensuring security by programmatically terminating active WhatsApp sessions.
Example: After completing a batch of automated messages, you might want to log out the WhatsApp instance to free resources or prevent unauthorized use.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra parameters for the logout operation. Includes: |
| - Reply to Message ID: ID of message to reply to (string) | |
| - Delay (seconds): Delay before sending message (number) | |
| - Disable Link Preview: Whether to disable link previews in messages (boolean) | |
| - Mention Users: Comma-separated phone numbers to mention in the message (string) |
Note: For the Logout operation under the Instance resource, only the Additional Fields collection is available as input properties.
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 request.
Example output JSON structure:
{
"status": "success",
"message": "Instance logged out successfully"
}
If an error occurs, the output JSON 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 (
https://n8ntools.io/api/v1/proxy/uazapi) which requires an additional API key credential for authentication.Proper configuration of these credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or expired API tokens can cause authentication failures.
- Incorrect instance ID may result in errors indicating the instance was not found.
- Network connectivity problems to the proxy or Uazapi endpoints.
Error messages:
"Unauthorized"or"Invalid API token": Check that the API token and API key credentials are correct and have not expired."Instance not found": Verify the instance ID is correct and the instance is active."Request failed"or timeout errors: Ensure network access to the proxy URL and Uazapi service is available.
Resolution tips:
- Re-enter or refresh API credentials.
- Confirm instance ID matches the intended WhatsApp instance.
- Test connectivity outside n8n using tools like curl or Postman.
Links and References
- Uazapi Official Documentation (example 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.