WTS Chat icon

WTS Chat

Get data from Wts API

Overview

The node "WTS Chat" integrates with the Wts API to manage chat-related data and operations. Specifically, for the Message resource and the Get Message Status operation, it retrieves the current status of a message by its unique identifier. This is useful in scenarios where you want to track whether a message has been delivered, read, failed, or is still pending.

Practical examples include:

  • Monitoring message delivery status in customer support workflows.
  • Triggering follow-up actions based on message state (e.g., retry sending if failed).
  • Reporting and analytics on communication effectiveness.

Properties

Name Meaning
Message ID The unique identifier of the message whose status you want to retrieve.

Output

The output is a JSON object containing the status information of the specified message. The exact structure depends on the Wts API response but typically includes fields such as message ID, current status (e.g., sent, delivered, read), timestamps, and possibly error details if applicable.

If the node supports binary data output for other operations, it is not relevant here since this operation only returns JSON status data.

Dependencies

  • Requires an API key credential for authenticating with the Wts API.
  • The base URL for API requests is https://api.wts.chat.
  • No additional environment variables are explicitly required beyond the API key credential.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty Message ID will likely cause errors.
    • Network or authentication failures can prevent retrieving message status.
  • Error messages:

    • "NodeApiError" wrapping errors from the Wts API calls.
    • If the Message ID is missing or invalid, the node may throw an error indicating that the input is required or invalid.
  • Resolution:

    • Ensure the Message ID is correctly provided and corresponds to an existing message.
    • Verify that the API key credential is valid and has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion