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 → Get session health
AI-generatedOverview
This node integrates with the WaliChat WhatsApp API to perform various operations related to WhatsApp messaging and management. Specifically, for the WhatsApp session resource with the Get session health operation, it retrieves the current health status of a specified WhatsApp session (device). This is useful for monitoring whether a WhatsApp number's session is active, connected, or experiencing issues.
Practical scenarios include:
- Automatically checking if a WhatsApp number is ready to send and receive messages.
- Monitoring session connectivity to trigger alerts or retries in workflows.
- Ensuring that automated messaging campaigns only run when sessions are healthy.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) whose session health you want to check. Options are dynamically loaded from available devices. |
Output
The node outputs a JSON object containing the session health information for the specified WhatsApp number. The exact structure depends on the API response but typically includes fields such as connection status, last seen time, and any error or warning messages related to the session.
If the node supports binary data output, it is not relevant for this operation and thus not applicable here.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API.
- The node relies on dynamic loading of WhatsApp numbers (devices), so proper configuration and permissions to access device lists are necessary.
- Network connectivity to the WaliChat API endpoint is required.
Troubleshooting
Common Issues:
- Invalid or expired API key leading to authentication errors.
- Specifying a WhatsApp number that does not exist or is not linked to the account.
- Network issues causing timeouts or failed API calls.
Error Messages:
"error": "Invalid API key": Check and update the API key credential."error": "Device not found": Verify the WhatsApp number ID is correct and available.- Timeout or network errors: Ensure stable internet connection and API endpoint accessibility.
Links and References
- WaliChat API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes