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 perform various operations related to WhatsApp messaging and management. Specifically, for the WhatsApp session resource with the Get session health operation, it retrieves the health status of a particular WhatsApp session associated with a given WhatsApp number.
This functionality is useful in scenarios where you need to monitor the connectivity or operational status of WhatsApp sessions linked to your numbers, ensuring that messages can be sent and received without issues. For example, before sending bulk messages or automating customer support chats, you might want to verify that the session is active and healthy.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) whose session health you want to check. This is selected from available WhatsApp numbers linked to your account. |
Output
The node outputs a JSON object containing the session health information for the specified WhatsApp number. This typically includes details such as connection status, uptime, errors if any, and other relevant health metrics provided by the Wassenger API.
If the node supports binary data output (not indicated here), it would represent media or files related to the session, but for this operation, the output is purely JSON-based status information.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- The "WhatsApp Number" property dynamically loads available devices via a method named
getDevices, which implies the node fetches device options from the API or internal configuration.
Troubleshooting
Common Issues:
- Invalid or expired API key leading to authentication failures.
- Specifying a WhatsApp number (device) that does not exist or is not linked to the account.
- Network connectivity problems preventing access to the Wassenger API.
- Session may report unhealthy if the WhatsApp client is disconnected or logged out.
Error Messages:
- Errors returned from the API will be caught and can appear in the output JSON under an
errorfield if "Continue On Fail" is enabled. - Authentication errors usually indicate invalid credentials; recheck and update the API key.
- Device not found errors suggest the selected WhatsApp number is incorrect or unavailable.
- Errors returned from the API will be caught and can appear in the output JSON under an
To resolve these, ensure valid credentials, correct device selection, and stable network connectivity.
Links and References
- Wassenger Official Website
- Wassenger API Documentation (for detailed API endpoints and session health info)
- n8n Documentation on Creating Custom Nodes