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
The "Archive Chat" operation in the Chats resource allows users to archive a specific WhatsApp chat associated with a given WhatsApp number (device). Archiving a chat typically means marking it as archived on the WhatsApp platform, which helps in organizing conversations by hiding them from the main chat list without deleting them.
This node operation is beneficial for automating chat management workflows, such as:
- Automatically archiving chats after they are resolved or inactive.
- Organizing chats programmatically based on business rules.
- Integrating WhatsApp chat status updates into broader CRM or support systems.
For example, a customer support system could use this operation to archive chats once a ticket is closed, keeping the agent's chat list clean and focused on active conversations.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to perform the operation on. This corresponds to the WhatsApp account or phone number used. Options are dynamically loaded from available devices. |
| Chat ID | The unique identifier of the chat to archive. Examples include user chats like 447362053576@c.us or group chats like 44736205357600000000@g.us. |
Output
The output JSON contains the response from the WhatsApp API after attempting to archive the specified chat. It typically includes confirmation of the action or details about the updated chat status.
If the node supports binary data output (not indicated here), it would represent any files or media related to the chat, but for this operation, the output is purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger WhatsApp API service to perform chat operations.
- The "WhatsApp Number" must be registered and accessible via the connected Wassenger account.
- Dynamic loading of WhatsApp numbers (devices) is supported through a method that fetches available devices.
Troubleshooting
Common Issues:
- Invalid or missing Chat ID: Ensure the chat ID is correctly formatted and exists.
- Unauthorized errors: Verify that the API key credential is valid and has permissions.
- Device not found: Confirm that the selected WhatsApp number (device) is active and linked to the Wassenger account.
Error Messages:
"error": "Chat not found": The provided Chat ID does not exist or is incorrect."error": "Unauthorized": Authentication failed; check API key credentials."error": "Device not registered": The WhatsApp number is not recognized; reload device options or verify device setup.
Resolving these usually involves verifying input parameters, refreshing credentials, or checking the Wassenger dashboard for device status.
Links and References
- Wassenger API Documentation โ Official API docs for managing WhatsApp chats and other resources.
- WhatsApp Chat IDs Format โ Explanation of chat ID formats for users and groups.