Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Transfer Session" operation in the WTS Chat node allows users to transfer an active chat session either to a different department or directly to a specific user within a department. This is useful in customer support or sales scenarios where conversations need to be routed dynamically based on workload, expertise, or organizational structure.
For example, if a customer inquiry requires specialized knowledge, the session can be transferred from a general support department to a technical team. Alternatively, it can be assigned to a particular agent for personalized handling.
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 expression. If not set, the session will not be transferred to a department. |
| User Name or ID | The target user within the selected department to whom the session should be assigned. This list updates dynamically based on the chosen department. If not set, the session will be transferred only to the department. |
Output
The output JSON contains the response from the API call that performs the session transfer. It typically includes details about the updated session state after the transfer, such as new department and/or user assignment confirmation.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the WTS Chat API.
- The node uses the WTS Chat service endpoint to perform the transfer.
- The "Department Name or ID" and "User Name or ID" options are dynamically loaded via methods that fetch available departments and users from the API.
Troubleshooting
- Missing Session ID: If the "Session ID" property is empty, the node throws an error prompting to fill in this required field.
- Invalid Department/User Selection: If a department is selected but no user is chosen when required, the node defaults to transferring to the department only.
- API Errors: Any errors returned by the WTS Chat API during the transfer process are caught and surfaced as node errors with descriptive messages.
- Permission Issues: Ensure the API key used has sufficient permissions to update session assignments.
- Dynamic Options Loading: If the department or user lists fail to load, verify network connectivity and API credentials.
Links and References
- WTS Chat API Documentation (generic placeholder link)
- n8n Expressions Documentation - for specifying dynamic values in properties
This summary focuses exclusively on the "Transfer Session" operation under the "Session" resource as requested.