Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node interacts with the Wassenger WhatsApp API, specifically allowing management of WhatsApp sessions. The "Reset session" operation for the "WhatsApp session" resource enables users to reset a WhatsApp device session by clearing stored data or queued messages and optionally waiting for the device to become available again.
Common scenarios include:
- Clearing all chat history, contacts, and messages from a WhatsApp device session to start fresh.
- Emptying the message queue to remove pending outgoing messages.
- Resetting a device session while ensuring the device is ready before proceeding, useful in automation workflows that depend on device availability.
Practical example:
- A user wants to reset a WhatsApp number's session to clear all stored chats and messages before switching to a new campaign, ensuring no old data interferes with new communications.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to reset. |
| Options | Collection of options to customize the reset behavior: |
| - Delete All Data | Whether to delete all stored chats, messages, and contacts data. |
| - Wait For Session | Whether to wait for the device to be available after reset (may delay response up to 2 minutes). |
| - Empty Queue | Whether to delete all queued messages in the current device. |
Output
The node outputs JSON data representing the result of the reset session operation. This typically includes confirmation of the reset action and any relevant status information returned by the Wassenger API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and the specified WhatsApp number (device) being registered and active.
- Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number ID may cause the reset operation to fail.
- Network or authentication errors if the API key is incorrect or the Wassenger service is unreachable.
- If "Wait For Session" is enabled, the operation might take up to 2 minutes; timeouts or delays could occur if the device does not become available.
Error messages:
- Errors related to invalid device ID usually indicate the WhatsApp number was not found or is not linked.
- Authentication errors suggest checking the API key credential setup.
- Timeout errors when waiting for the session imply the device did not respond in time; consider disabling the wait option or verifying device connectivity.