WTS Chat icon

WTS Chat

Get data from Wts API

Actions17

Overview

This node integrates with the WTS Chat API to perform various operations related to contacts, messages, sessions, and panels. Specifically for the Message resource and the Get Message Status operation, it retrieves the current status of a message by its unique identifier.

Common scenarios where this node is beneficial include:

  • Tracking delivery or read status of sent messages in customer support or marketing workflows.
  • Monitoring message lifecycle events to trigger follow-up actions or notifications.
  • Integrating message status checks into automated processes for reporting or analytics.

For example, after sending a message via the WTS Chat platform, you can use this node to query the message status (e.g., delivered, read, failed) by providing the message ID, enabling real-time updates in your workflow.

Properties

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

Output

The node outputs an array of JSON objects representing the message status information returned from the WTS Chat API. The exact structure depends on the API response but typically includes fields such as:

  • Message ID
  • Current status (e.g., sent, delivered, read)
  • Timestamps related to status changes
  • Any relevant metadata about the message state

No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "messageId": "12345",
  "status": "DELIVERED",
  "deliveredAt": "2024-06-01T12:34:56Z"
}

Dependencies

  • Requires an active API key credential for the WTS Chat API.
  • The base URL used for requests is https://api-test.helena.run.
  • Uses HTTP GET requests with Bearer token authorization to fetch message status.

Troubleshooting

  • Invalid or missing Message ID: Ensure that the Message ID provided is correct and corresponds to an existing message in the system.
  • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
  • Network or API errors: Temporary network issues or API downtime may cause request failures; retrying later might help.
  • Empty or unexpected responses: Confirm that the message exists and that the API endpoint is functioning as expected.

If the node returns no data or an error, check the input parameters and credentials configuration.

Links and References

Discussion