Actions17
- Contact Actions
- Message Actions
- Session Actions
- Panel Actions
Overview
The "Update Session" operation in the WTS Chat node allows users to transfer a chat session to a different department or assign it 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 initially handled by a general support team needs escalation to a specialized technical team, this operation can update the session's assignment accordingly. Similarly, it can reassign a session to a particular agent for personalized handling.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the chat session to update. |
| Departments Name or ID | The target department to which the session should be transferred. Can be selected from a list or specified via expression. |
| User Name or ID | The specific user within the department to whom the session should be assigned. Updates dynamically based on chosen department. |
Output
The output JSON contains the updated session information returned from the API after the transfer operation. It typically includes details such as the new department and/or user assignment, session status, timestamps, and other metadata reflecting the current state of the session.
No binary data is involved in this operation.
Dependencies
- Requires an active API key credential for authentication with the WTS Helena API.
- The node makes HTTP PUT requests to the endpoint
/chat/v1/session/{sessionId}/transferon the base URLhttps://api-test.helena.run. - The department and user options are dynamically loaded using helper methods that query the API for available departments and users.
Troubleshooting
- Invalid Session ID: If the provided session ID does not exist or is malformed, the API will likely return an error. Verify the session ID before running the node.
- Missing Department or User: If neither department nor user is specified, the request payload may be invalid. At least one must be provided to define the transfer target.
- Authorization Errors: Ensure the API key credential is valid and has sufficient permissions to update sessions.
- Network Issues: Connectivity problems to the API endpoint will cause failures; check network access and proxy settings if applicable.
Links and References
- n8n Expressions Documentation
- WTS Helena API documentation (not publicly linked here) for detailed API endpoint behavior and data models.