Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Transfer Session" operation in the WTS Chat node allows transferring an active chat session to a different department or 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.
Typical use cases include:
- Automatically transferring a chat session to a specialized department (e.g., billing, technical support).
- Assigning a session to a particular agent or user within a department for personalized handling.
- Escalating or reassigning sessions to ensure timely and appropriate responses.
For example, when a customer requests help with billing, the session can be transferred from a general support queue to the billing department or directly to a billing specialist.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the chat session to transfer. |
| Department Name or ID | The target department to which the session should be transferred. Can be selected from a list or specified by ID. Use "Undefined" to skip sending this parameter. |
| User Name or ID | The target user within the selected department to assign the session to. This list updates based on the chosen department. Use "Undefined" to skip specifying a user. |
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 or user assignment confirmation.
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the WTS Chat API.
- The node depends on the WTS Chat service endpoints to perform session transfers.
- 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 it in. Ensure the session ID is provided.
- Invalid Department/User Selection: If a department is selected but no user is specified, the transfer defaults to the department level. If both are missing or invalid, the API may reject the request.
- API Errors: Any errors returned by the WTS Chat API during transfer will be surfaced as node errors. Check the API key validity and network connectivity.
- Rate Limits: When processing multiple items, the node includes a delay to avoid hitting rate limits. Excessive rapid calls might still cause throttling.
Links and References
- WTS Chat API Documentation (general reference)
- n8n Expressions Documentation — for using expressions in property fields like Department or User IDs.