WTS Chat icon

WTS Chat

Get data from Wts API

Overview

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

Common scenarios where this node is beneficial include:

  • Fetching the content and metadata of a specific chat message for auditing or processing.
  • Integrating chat message data into workflows for customer support, analytics, or CRM updates.
  • Automating retrieval of message details to trigger further actions based on message content or status.

For example, you might use this node to get the full details of a message received in a customer support chat session to analyze the conversation or update a ticketing system.

Properties

Name Meaning
Message ID The unique identifier of the message to retrieve.

Output

The output of this operation is a JSON object representing the message details as returned by the WTS Chat API. This typically includes fields such as message content, sender, timestamp, status, and any associated metadata.

The output structure is:

{
  "json": {
    // Full message object as returned by the API
  }
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the WTS Chat API.
  • The base URL used for API calls is https://api-test.helena.run.
  • Uses the Axios HTTP client internally to make REST API calls.

Troubleshooting

  • Invalid or missing Message ID: Ensure that the Message ID provided is correct and not empty.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network or API errors: Check network connectivity and confirm the WTS Chat API service is operational.
  • Empty or no response: If the message does not exist or was deleted, the API may return an error or empty result; handle such cases gracefully in your workflow.

Links and References

Discussion