WTS Chat icon

WTS Chat

Get data from Wts API
Join our community

Actions39

Overview

This node interacts with the WTS Chat API to perform various operations related to chat messages, contacts, sessions, panels, chatbots, and sequences. Specifically, for the 'Message' resource and 'Get All Messages' operation, it retrieves all messages associated with a given session ID, supporting filtering and pagination options. This is useful for scenarios where users need to fetch chat history or message logs from a specific session for analysis, reporting, or further processing.

Use Case Examples

  1. Retrieve all messages from a specific chat session by providing the session ID.
  2. Fetch messages within a certain date range using createdAt or updatedAt filters.
  3. Automatically paginate through multiple pages of messages to gather a complete message history.

Properties

Name Meaning
Session ID The unique identifier of the chat session to retrieve messages from.
CreatedAt.After Filter to include messages created after this date and time.
CreatedAt.Before Filter to include messages created before this date and time.
UpdatedAt.After Filter to include messages updated after this date and time.
UpdatedAt.Before Filter to include messages updated before this date and time.
Auto Pagination Whether to automatically paginate through multiple pages of results to retrieve more messages.
Max Pages Maximum number of pages to retrieve when auto pagination is enabled.
Page Number The specific page number to retrieve when auto pagination is disabled.
Page Size Number of messages to retrieve per page when auto pagination is disabled.
Order By Field to sort the messages by.
Order Direction Direction of sorting the messages, either ascending or descending.

Output

JSON

  • json - The retrieved messages data from the WTS Chat API, including message details such as content, timestamps, sender information, and session association.

Dependencies

  • WTS Chat API

Troubleshooting

  • Ensure the 'Session ID' is provided and not empty; otherwise, the node throws an error indicating the session ID is required.
  • If using file inputs for sending messages, verify that the binary data exists and the file name matches the input parameter; missing files cause errors.
  • Check API key credentials are correctly configured and valid to avoid authentication errors.
  • When using pagination, ensure page numbers and sizes are within allowed ranges to prevent request failures.

Discussion