Actions39
- Panel Actions
- Message Actions
- Chatbot Actions
- Contact Actions
- Sequence Actions
- Session Actions
Overview
This node operation transfers a chat session to a different department or user within the WTS Chat system. It is useful in scenarios where a chat session needs to be reassigned for better handling, such as transferring a customer support session to a specialized department or a specific agent. For example, if a customer inquiry requires escalation, this operation can transfer the session to the appropriate team or user.
Use Case Examples
- Transferring a customer support chat session from a general department to a technical support department.
- Reassigning a chat session from one agent to another for workload balancing.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the chat session to be transferred. |
| Department Name or ID | The target department to which the session should be transferred. Can be selected from a list or specified by ID. |
| User Name or ID | The target user within the selected department to whom the session should be assigned. This list updates based on the selected department and can be specified by ID. |
Output
JSON
json- The response object from the WTS Chat API after transferring the session, containing details of the updated session transfer status.
Dependencies
- Requires an API key credential for WTS Chat API authentication.
Troubleshooting
- Ensure the Session ID is provided; otherwise, the node throws an error indicating the session ID field must be filled.
- If specifying a department, ensure the user ID is either provided or omitted correctly to avoid transfer type conflicts.
- API errors from the WTS Chat service are wrapped and thrown as node errors; check API key validity and network connectivity if errors occur.
Links
- n8n Expressions Documentation - Guidance on using expressions to specify dynamic values for properties like Department ID or User ID.