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
WhatsApp session → Reboot session
AI-generatedOverview
The "Reboot session" operation under the "WhatsApp session" resource allows users to reboot a specific WhatsApp device session. This can be useful in scenarios where the WhatsApp session becomes unresponsive, disconnected, or requires a refresh to restore proper functionality. For example, if a WhatsApp number linked to the system stops syncing messages or shows connectivity issues, rebooting the session can help re-establish the connection without needing to reconfigure the entire integration.
Practical examples:
- Force reboot a WhatsApp device session that is stuck or not responding.
- Wait for the session to become available after reboot before proceeding with further actions.
- Force synchronization of the device session immediately after reboot to ensure message consistency.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to reboot. Loaded dynamically from available devices. |
| Options | Collection of optional flags to control reboot behavior: |
| - Force Reboot | Whether to force the device reboot even if it is already stopped (boolean). |
| - Wait For Session | Whether to wait for the device session to become available after reboot, which may delay response up to 90 seconds (boolean). |
| - Force Sync | Whether to force device synchronization immediately after reboot (boolean). |
Output
The node outputs JSON data representing the result of the reboot operation on the specified WhatsApp device session. The exact structure depends on the underlying API response but generally includes status information about the reboot command and possibly session state details.
If the node supports binary data output, it is not indicated here; thus, the output is primarily JSON-based.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API service.
- The node relies on dynamic loading of WhatsApp device IDs via a method named
getDevices. - No additional external dependencies are explicitly required beyond the configured API key and network access to the WaliChat API.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp device ID: Ensure the selected WhatsApp number exists and is correctly loaded.
- API authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Timeout when waiting for session availability: If "Wait For Session" is enabled, the operation might take up to 90 seconds; network delays or server issues could cause longer waits or failures.
Error Messages:
- Errors returned by the API will be surfaced as error messages in the node output unless "Continue On Fail" is enabled.
- Typical errors include invalid device ID, unauthorized access, or internal server errors.
Resolutions:
- Double-check device selection and API credentials.
- Retry the operation if transient network or server issues occur.
- Disable "Wait For Session" if immediate response is preferred and session availability is not critical.
Links and References
- WaliChat WhatsApp API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes
- General WhatsApp Business API concepts for session management.