WTS Chat

Overview

The "Transfer to User" operation within the "Session" resource of this node allows transferring an active chat session to a specific user. This is useful in customer support or sales scenarios where a conversation needs to be handed off from an automated system, bot, or general queue to a particular agent or team member for personalized handling.

Typical use cases include:

• Escalating a chat session to a specialized support agent.
• Assigning a session to a user based on workload balancing.
• Manually routing conversations to users with specific expertise.

For example, after identifying that a customer's issue requires human intervention, this node can transfer the session by specifying the session ID and the target user's ID or username.

Properties

Output

The output JSON contains the result of the transfer operation as returned by the underlying API service. It typically includes details about the updated session assignment, such as confirmation of the new user assignment or any relevant metadata about the session state after transfer.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "json": {
    "sessionId": "string",
    "assignedUserId": "string",
    "status": "string",
    "updatedAt": "timestamp"
  }
}

Dependencies

• Requires an API key credential for authenticating requests to the WTS Chat API.
• The node depends on the external WTS Chat service endpoint to perform session transfers.
• Proper configuration of the API base URL and credentials in n8n is necessary.

Troubleshooting

• Empty Session ID: If the "Session ID" property is empty or whitespace, the node throws an error indicating the field must be filled.
• Empty or Invalid User ID: If the "User Name or ID" is not selected or set to the default "Undefined", an error is thrown prompting to choose a valid user.
• API Errors: Any errors returned by the external API during the transfer process are caught and rethrown as node errors with descriptive messages.
• Network Issues: Connectivity problems with the WTS Chat API may cause timeouts or failures; ensure network access and correct API endpoint configuration.

To resolve these issues:

• Verify all required fields are correctly filled.
• Confirm the API key credential is valid and has sufficient permissions.
• Check network connectivity and API availability.
• Use expressions carefully when specifying user IDs to avoid invalid values.

Links and References

• WTS Chat API Documentation (generic link, replace with actual docs if available)
• n8n Expressions Documentation - for using expressions in property fields