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 manage WhatsApp chats programmatically. Specifically, the Unassign Chat operation under the Chats resource allows users to unassign a chat from an agent or user within their WhatsApp management system.
Common scenarios where this node is beneficial include:
- Automatically unassigning chats when an agent finishes handling a conversation.
- Releasing chats back to a queue for reassignment.
- Managing workload distribution by dynamically unassigning chats based on business logic.
For example, after a customer support interaction completes, you can use this node to unassign the chat so it becomes available for other agents.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the chat originates. |
| Chat ID | The unique identifier of the chat to be unassigned. It can represent individual or group chats (e.g., 447362053576@c.us for a user, 44736205357600000000@g.us for a group). |
Output
The node outputs JSON data representing the result of the unassignment operation. This typically includes confirmation that the chat was successfully unassigned or details about the updated chat state.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Wassenger WhatsApp API via an API key credential.
- The node depends on the Wassenger API being accessible and properly configured in n8n credentials.
- The "WhatsApp Number" must be a valid device registered in the Wassenger system.
Troubleshooting
- Invalid Chat ID: If the provided Chat ID does not exist or is malformed, the API may return an error. Verify the chat ID format and existence.
- Unauthorized Access: Ensure the API key credential has sufficient permissions to modify chat assignments.
- Device Not Found: The WhatsApp Number (device) must be valid and active; otherwise, the operation will fail.
- Network Issues: Connectivity problems with the Wassenger API endpoint can cause timeouts or errors.
To resolve these issues:
- Double-check input parameters for correctness.
- Confirm API key validity and permissions.
- Verify network connectivity and API service status.
Links and References
- Wassenger Official API Documentation (for detailed API capabilities and chat management)
- n8n Documentation (for general guidance on using custom nodes and credentials)