WTS Chat icon

WTS Chat

Get data from Wts API

Actions38

Overview

The "Get All Cards" operation under the "Panel" resource retrieves a list of cards from a specified panel in the WTS Chat system. This operation allows filtering and refining the results based on various criteria such as step within the panel, contact ID, responsible user, text filters, archived status, and additional details to include.

This node is beneficial when you want to programmatically access all cards related to a specific panel for purposes like reporting, automation workflows, or integration with other systems. For example, you could use it to fetch all active tasks (cards) assigned to a particular user or filter cards by certain keywords in their titles or descriptions.

Properties

Name Meaning
Panel Name or ID Choose the panel from which to retrieve cards. You can select from a list or specify an ID using an expression.
Step Name or ID Optionally choose a specific step within the selected panel to filter cards belonging to that step.
Contact ID Filter cards associated with a specific contact by providing the contact's ID.
User Name or ID Filter cards assigned to a specific responsible user by selecting from a list or specifying an ID via expression.
Text Filter Enter a text string to filter cards whose content matches the given text.
Include Archived Boolean flag indicating whether to include archived cards in the results. Defaults to false (exclude archived).
Include Details Multi-select option to include additional related information in the response. Options include: Contacts, CustomFields, PanelTitle, ResponsibleUser, StepPhase, StepTitle.
CreatedAt.After Filter cards created after this date/time (format: YYYY-MM-DD hh:mm, timezone-aware).
CreatedAt.Before Filter cards created before this date/time.
UpdatedAt.After Filter cards updated after this date/time.
UpdatedAt.Before Filter cards updated before this date/time.
Auto Pagination Whether to automatically paginate through multiple pages of results, aggregating them into one output.
Max Pages When auto pagination is enabled, limits the maximum number of pages to retrieve (1-100).
Page Number When auto pagination is disabled, specifies which page of results to retrieve.
Page Size Number of items per page when auto pagination is disabled (1-100).
Order By Field name to sort the results by.
Order Direction Direction of sorting: Ascending or Descending. Defaults to Ascending.

Output

The output is an array of JSON objects representing the cards retrieved from the specified panel. Each card object contains fields describing the card's properties such as title, description, position, monetary amount, associated contacts, tags, responsible user, custom fields, metadata, and status (archived or not).

If the "Include Details" property is used, the output will also contain nested objects or arrays with additional related data such as contact details, custom fields definitions, panel title, responsible user info, step phase, and step title.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the WTS Chat API.
  • The node uses the WTS CRM service internally to fetch panel and card data.
  • Network connectivity to https://api.wts.chat is required.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Missing Panel ID: If the "Panel Name or ID" property is not set or left as undefined, the node will throw an error indicating the panel ID field must be filled.
  • API Authentication Errors: If the API key is invalid or missing, the node will fail with authentication errors. Ensure the API key credential is correctly configured.
  • Empty Results: If no cards match the filter criteria, the output will be an empty array.
  • Invalid Date Filters: Date/time filters must be in the correct format (YYYY-MM-DD hh:mm) and respect time zones; otherwise, the API may reject the request.
  • Pagination Misconfiguration: Using auto pagination without setting a reasonable max pages limit may result in long execution times or large outputs.
  • Network Issues: Connectivity problems to the WTS API endpoint will cause failures; verify network access.

Links and References

Discussion