WTS Chat

Overview

The node interacts with the "Panel" resource of the WTS Chat API, specifically supporting the operation Get Card By ID. This operation retrieves detailed information about a specific card within a panel by its unique identifier.

This node is useful in scenarios where you need to fetch comprehensive data about a particular card in a project management or CRM-like panel system. For example, you might want to retrieve all details of a task card to display its status, assigned user, custom fields, and related contacts in an automation workflow.

Practical examples:

• Fetching a card's details to update a dashboard or report.
• Retrieving card information before performing updates or duplications.
• Accessing card metadata and custom fields for integration with other systems.

Properties

Output

The output is a JSON object representing the card data retrieved from the API. It includes the card's core properties such as title, description, position, monetary amount, associated contacts, tags, responsible user, and any custom fields or metadata.

If "Include Details" options are selected, the output will also contain nested objects or arrays with detailed information about those aspects (e.g., full contact details, custom fields definitions, panel titles, user info, step phases, and titles).

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the WTS Chat API via an API key credential.
• The node uses the WtsCrmService.getCardById method internally to fetch card data.
• Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

• Error: "CardID is empty, please fill it in"
  Occurs if the Card ID property is not provided. Ensure that the Card ID field is filled with a valid identifier.

• API errors wrapped as NodeApiError
  These indicate issues returned from the WTS Chat API, such as invalid IDs, permission issues, or network problems. Check the error message for specifics and verify API access and parameters.

• Empty or incomplete data returned
  If the card exists but some expected details are missing, verify if the "Include Details" property is set correctly to fetch related entities.

Links and References

• WTS Chat API Documentation (general base URL referenced in code)
• n8n Documentation on Creating Custom Nodes
• General REST API best practices for handling authentication and pagination

This summary is based solely on static analysis of the provided source code and input property definitions.