WTS Chat

Overview

The node "WTS Chat" integrates with the WTS API to manage chat sessions and related entities. Specifically, the Get Session By ID operation retrieves detailed information about a particular chat session using its unique session ID. This operation can optionally include additional details such as agent info, channel info, classification, contact, departments, etc.

This node is useful in scenarios where you need to fetch comprehensive data about a specific chat session for monitoring, reporting, or further processing within an automation workflow. For example, customer support teams can use it to pull session details to analyze interactions or escalate issues.

Properties

These properties allow users to specify which session to fetch and what extra related information should be included in the output.

Output

The output is a JSON object representing the session data retrieved from the WTS API. It includes the core session information identified by the given Session ID, plus any optional detailed sections requested via the "Include Details" property.

The structure typically contains fields such as session metadata, status, timestamps, associated agents, channels, contacts, classifications, and department info depending on the included details.

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the WTS API.
• Needs an API key credential configured in n8n for authentication.
• The base URL for API requests is https://api.wts.chat.
• The node depends on internal services (WtsChatService) to perform the API call to get session details.

Troubleshooting

• SessionID is empty!
  Error thrown if the Session ID parameter is missing or blank. Ensure the Session ID is provided and correctly formatted.

• API errors
  If the API key is invalid or the session ID does not exist, the node will throw an error with details from the WTS API. Verify credentials and session ID correctness.

• Network issues
  Connectivity problems to the WTS API endpoint may cause timeouts or failures. Check network access and proxy settings if applicable.

• Invalid Include Details options
  Providing unsupported values in the "Include Details" multi-select might result in incomplete or failed responses. Use only the documented options.

Links and References

• WTS API Documentation (Assumed official docs URL, replace with actual if known)
• n8n Documentation on Creating Custom Nodes
• General info on Chat Session Management

This summary is based solely on static analysis of the provided source code and input property definitions.