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 to manage WhatsApp sessions among many other resources. Specifically, the "Reboot session" operation under the "WhatsApp session" resource allows users to reboot a WhatsApp device session remotely. This can be useful in scenarios where a WhatsApp session becomes unresponsive or needs to be refreshed without manual intervention on the device.
Practical examples include:
- Automatically rebooting a WhatsApp session if message sending fails due to session issues.
- Forcing a session reboot during maintenance windows to ensure fresh connections.
- Waiting for the session to become available after reboot before proceeding with further automation steps.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to reboot. |
| Options | Collection of optional flags to control reboot behavior: |
| - Force Reboot | Whether to force device reboot even if the session is already stopped (true/false). |
| - Wait For Session | Whether to wait for the device session to become available after reboot (may delay response up to 90 seconds). |
| - Force Sync | Whether to force device synchronization after reboot (true/false). |
Output
The node outputs JSON data representing the result of the reboot operation. This typically includes status information about the reboot request and possibly updated session state details. The exact structure depends on the API response from Wassenger.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node relies on the Wassenger API service being accessible and properly configured.
- The "WhatsApp Number" options are dynamically loaded via a method that fetches available devices from the API.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp number/device ID will cause the reboot to fail.
- Network connectivity problems may prevent communication with the Wassenger API.
- If "Wait For Session" is enabled, the node may take up to 90 seconds to respond; timeouts could occur if the session does not become available.
Error Messages:
- Errors returned by the API will be surfaced as messages in the node output when "Continue On Fail" is enabled.
- Authentication errors indicate invalid or expired API keys; reconfigure credentials accordingly.
- Device not found or session not active errors suggest checking the selected WhatsApp number.