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 integrates with the Wassenger WhatsApp API to synchronize recent chats from a specified WhatsApp device (phone number). It fetches a limited number of recent chats along with a configurable maximum number of messages per chat. This is useful for scenarios where you want to back up, analyze, or process WhatsApp conversations programmatically within an n8n workflow.
Practical examples:
- Syncing recent customer support chats from a WhatsApp business number to a CRM system.
- Archiving recent conversations for compliance or auditing purposes.
- Triggering workflows based on new messages in synced chats.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number (device) | The ID of the WhatsApp number/device from which to sync chats. |
| Maximum Chats (size) | The maximum number of recent chats to synchronize (default is 50). |
| Maximum Messages Per Chat (messages) | The maximum number of messages to retrieve per chat (default is 50). |
Output
The node outputs an array of JSON objects representing the synchronized chats. Each object contains details about a chat and includes up to the specified maximum number of recent messages for that chat.
If binary data is present (e.g., media files in messages), it would be included accordingly, but this specific operation focuses on syncing chat metadata and messages primarily in JSON format.
Dependencies
- Requires an active Wassenger WhatsApp API account.
- Needs an API key credential configured in n8n to authenticate requests to the Wassenger API.
- The node depends on the Wassenger API's availability and permissions granted to the API key.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Specifying a WhatsApp number/device ID that does not exist or is not linked to the Wassenger account will result in errors.
- Requesting too many chats or messages may lead to rate limiting or timeouts depending on API limits.
Error messages:
- Authentication errors typically indicate invalid credentials; verify and update the API key.
- "Device not found" or similar errors suggest the WhatsApp number ID is incorrect or not accessible.
- Timeout or rate limit errors can be mitigated by reducing the "Maximum Chats" or "Maximum Messages Per Chat" values.
Links and References
- Wassenger Official Website
- Wassenger API Documentation (for detailed API capabilities and limitations)