WTS Chat icon

WTS Chat

Get data from Wts API

Actions38

Overview

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

Common scenarios where this node is beneficial include:

  • Fetching the content and metadata of a particular chat message for auditing or processing.
  • Integrating message data into workflows that require message details for decision-making or logging.
  • Retrieving message status or history in customer support automation.

Practical example:

  • A workflow triggers when a new message ID is received, then uses this node to fetch the full message details to analyze or forward the content.

Properties

Name Meaning
Message ID The unique identifier of the message to retrieve. This must be provided as a string.

Output

The node outputs an array with one item containing a json object representing the message details fetched from the WTS Chat API. The structure of this JSON includes all relevant fields of the message such as content, sender, timestamps, status, and any other metadata provided by the API.

If the node supports binary data output (not applicable for this operation), it would represent files or media associated with messages, but for "Get Message By ID" the output is purely JSON.

Dependencies

  • Requires an active connection to the WTS Chat API via an API key credential.
  • The API key must be configured in the node credentials before execution.
  • Network access to https://api.wts.chat is necessary.

Troubleshooting

  • Error: Invalid or missing Message ID
    Ensure the "Message ID" property is correctly set and not empty. The node throws an error if the ID is missing or invalid.

  • API Authentication Errors
    If the API key is incorrect or missing, the node will fail to authenticate. Verify the API key credential configuration.

  • Network or API Errors
    Temporary network issues or API downtime can cause errors. Retry after some time or check API status.

  • NodeApiError Exceptions
    These wrap underlying API errors. Review the error message for specifics, such as "message not found" or permission issues.

Links and References

Discussion