WTS Chat icon

WTS Chat

Get data from Wts API

Actions39

Overview

The node interacts with the WTS Chat API to manage and retrieve data related to various resources such as contacts, messages, sessions, panels, sequences, and chatbots. Specifically for the Panel resource and the Get All Annotation operation, it retrieves all annotations associated with a specific card within a panel.

This operation is useful in scenarios where you want to fetch notes, comments, or other annotation data linked to a particular card in a project management or CRM system that uses panels and cards to organize information. For example, you might use this node to gather all feedback or updates recorded on a task card before generating reports or triggering further automation.

Properties

Name Meaning
Card ID The unique identifier of the card for which to list all annotations.
CreatedAt.After Filter annotations created after this date/time (format: YYYY-MM-DD hh:mm).
CreatedAt.Before Filter annotations created before this date/time (format: YYYY-MM-DD hh:mm).
UpdatedAt.After Filter annotations updated after this date/time (format: YYYY-MM-DD hh:mm).
UpdatedAt.Before Filter annotations updated before this date/time (format: YYYY-MM-DD hh:mm).
Auto Pagination Whether to automatically paginate through multiple pages of results.
Max Pages Maximum number of pages to retrieve when auto pagination is enabled (1 to 100).
Page Number The page number to retrieve when auto pagination is disabled.
Page Size Number of items per page when auto pagination is disabled (1 to 100).
Order By Field name by which to sort the annotations.
Order Direction Direction of sorting: Ascending or Descending.

Note: For the Get All Annotation operation, only the Card ID and generic pagination/filtering parameters are relevant.

Output

The output is an array of JSON objects, each representing an annotation linked to the specified card. Each annotation object contains details such as text content, file URLs if any, creation and update timestamps, and possibly metadata or custom fields depending on the annotation type.

The node does not output binary data for this operation; all data is returned as structured JSON.

Example output structure:

[
  {
    "id": "annotation-id",
    "cardId": "card-id",
    "text": "Annotation text content",
    "fileUrls": ["https://example.com/file1.png"],
    "createdAt": "2023-01-01T12:00:00Z",
    "updatedAt": "2023-01-02T15:30:00Z",
    "metadata": {...},
    "customFields": {...}
  },
  ...
]

Dependencies

  • Requires an active connection to the WTS Chat API via an API key credential.
  • The node expects the API key to be configured in n8n credentials for authentication.
  • No additional external dependencies are required beyond the WTS Chat API access.

Troubleshooting

  • Missing Card ID: If the Card ID parameter is empty or missing, the node will throw an error indicating that the Card ID must be provided.
  • API Errors: Network issues, invalid API keys, or permission problems may cause errors from the WTS Chat API. These errors are surfaced as node execution errors with descriptive messages.
  • Pagination Limits: When using auto pagination, setting an excessively high max pages value may lead to longer execution times or timeouts.
  • Date Filters Format: Date/time filters must be entered in the correct format (YYYY-MM-DD hh:mm) and respect the user's timezone to avoid unexpected filtering results.

Links and References

Discussion