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 "Assign Chat" operation within the "Chats" resource allows users to assign a WhatsApp chat to a specific agent, department, or both. This is useful in customer support or sales scenarios where incoming chats need to be routed to the appropriate team member or group for handling. For example, when a new customer message arrives, this node can automatically assign the chat to an available agent or a department responsible for that type of inquiry, ensuring efficient and organized communication management.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the chat originates or is managed. |
| Chat ID | The unique identifier of the chat to be assigned (e.g., user chat ID like 447362053576@c.us or group chat ID like 44736205357600000000@g.us). |
| Assignment Type | Method of assignment: - Agent ID - Agent Email - Department - Agent and Department |
| Agent ID | The ID of the agent to whom the chat will be assigned (required if Assignment Type includes agent). |
| Agent Email | The email address of the agent to assign the chat to (used if Assignment Type is "Agent Email"). |
| Department ID | The ID of the department to assign the chat to (required if Assignment Type includes department). |
Output
The node outputs JSON data representing the result of the chat assignment operation. This typically includes confirmation details such as the assigned agent or department information and status of the assignment. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the availability of configured WhatsApp numbers (devices), agents, and departments within the connected Wassenger account.
- Load options for properties like WhatsApp Number, Agent ID, and Department ID are dynamically fetched via methods integrated into the node.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp Number or Chat ID will cause the assignment to fail.
- Assigning to an agent or department that does not exist or is not linked to the selected WhatsApp number may result in errors.
- Using an incorrect assignment type without providing the corresponding required fields (e.g., selecting "Agent Email" but not providing an email) will cause validation errors.
Error Messages:
- Errors related to authentication usually indicate issues with the API key credential; ensure it is correctly set up.
- "Chat not found" or similar messages suggest the provided Chat ID is invalid or does not belong to the specified WhatsApp number.
- "Agent or Department not found" indicates the selected assignee does not exist or is unavailable for the chosen device.
Resolution Tips:
- Verify all input parameters carefully before execution.
- Ensure the WhatsApp number, agents, and departments are properly configured and accessible.
- Check API credentials and permissions.