WTS Chat

Overview

The node "WTS Chat" integrates with the Wts API to perform various operations related to chat, contacts, messages, sessions, panels, sequences, and chatbots. Specifically, for the Message resource and the Get Message By ID operation, the node retrieves detailed information about a specific message using its unique message ID.

This operation is useful when you want to fetch the content, metadata, status, or other details of a particular message in your chat system. For example, you might use it to audit message history, verify message delivery, or trigger workflows based on message content.

Properties

Output

The output of this operation is a JSON object representing the message data retrieved from the Wts API. This typically includes all relevant fields describing the message such as its content, sender, timestamp, status, and any associated metadata.

If the node supports binary data for other operations (e.g., sending files), that is handled separately, but for this operation, the output is purely JSON containing the message details.

Example output structure (conceptual):

{
  "id": "string",
  "content": "string",
  "sender": "string",
  "timestamp": "string",
  "status": "string",
  "metadata": { "key": "value" }
}

Dependencies

• Requires an API key credential for authenticating with the Wts API.
• The base URL for the API is https://api.wts.chat.
• The node depends on internal services (WtsChatService) to call the API endpoints.
• No additional environment variables are explicitly required beyond the API key credential.

Troubleshooting

• Common issues:
  • Providing an empty or invalid Message ID will cause the API call to fail.
  • Network or authentication errors if the API key is missing or invalid.
• Error messages:
  • "NodeApiError" wrapping the underlying API error, e.g., "Message not found" if the ID does not exist.
  • "Fill in the field" errors if required parameters are missing.
• Resolution:
  • Ensure the Message ID is correctly provided and valid.
  • Verify the API key credential is configured properly.
  • Check network connectivity to the Wts API endpoint.

Links and References

• Wts API Documentation (assumed official API docs)
• n8n documentation on creating custom nodes
• General info on handling API credentials in n8n workflows

This summary focuses solely on the Message resource and the Get Message By ID operation as requested.