WTS Chat icon

WTS Chat

Get data from Wts API
Join our community

Actions39

Overview

This node interacts with the WTS Chat API to manage "Panels" and their associated cards (tasks or items). Specifically, the "Get All Cards" operation retrieves a list of cards from a specified panel, optionally filtered by various criteria such as step, responsible user, contact, text content, and archival status. It supports including additional details about each card, such as contacts, custom fields, panel title, responsible user, step phase, and step title.

This operation is useful in scenarios where you want to automate workflows involving task management within panels, for example:

  • Fetching all active tasks assigned to a particular user or step.
  • Filtering cards by text content or contact association.
  • Including detailed metadata to enrich downstream processing or reporting.

Properties

Name Meaning
Panel Name or ID (panels) Select or specify the panel from which to retrieve cards. This is required.
Step Name or ID (stepPanels) Optionally filter cards by a specific step within the selected panel.
Contact ID (contactId) Optionally filter cards associated with a specific contact ID.
Responsible Name or ID (responsibleId) Optionally filter cards assigned to a specific responsible user.
Text Filter (textFilter) Optionally filter cards containing specific text.
Include Archived (includeArchived) Boolean flag to include archived cards in the results. Defaults to false.
Include Details (includeDetailsGetCards) Multi-select to include additional details in the response. Options: Contacts, CustomFields, PanelTitle, ResponsibleUser, StepPhase, StepTitle.
CreatedAt.After (createdAtAfter) Optional datetime filter to include cards created after this timestamp. Format: YYYY-MM-DD hh:mm (timezone-aware).
CreatedAt.Before (createdAtBefore) Optional datetime filter to include cards created before this timestamp.
UpdatedAt.After (updatedAtAfter) Optional datetime filter to include cards updated after this timestamp.
UpdatedAt.Before (updatedAtBefore) Optional datetime filter to include cards updated before this timestamp.
Auto Pagination (autoPagination) Whether to automatically paginate through multiple pages of results. Defaults to false.
Max Pages (maxPage) When auto pagination is enabled, limits the maximum number of pages to fetch. Default is 10.
Page Number (pageNumber) When auto pagination is disabled, specifies which page number to retrieve. Default is 1.
Page Size (pageSize) Number of items per page when auto pagination is disabled. Default is 15.
Order By (orderBy) Field name to sort the results by.
Order Direction (orderDirection) Sort direction: Ascending or Descending. Default is Ascending.

Output

The output is an array of JSON objects representing the cards retrieved from the specified panel. Each item contains the card's data, potentially enriched with additional details if requested via the "Include Details" property. The structure typically includes:

  • Card identifiers and titles.
  • Associated step and panel information.
  • Responsible user details.
  • Linked contacts.
  • Custom fields and metadata.
  • Archival status and timestamps.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the WTS Chat API.
  • The node depends on the WTS CRM service module to perform API calls related to panels and cards.
  • Network access to https://api.wts.chat is necessary.
  • Proper configuration of the API key credential in n8n is required.

Troubleshooting

  • Missing Panel ID: If the "Panel Name or ID" property is not set or is "Undefined", the node will throw an error indicating that the panel ID field must be filled.
  • API Errors: Any issues communicating with the WTS API (e.g., invalid API key, network errors) will result in errors wrapped as NodeApiError with descriptive messages.
  • Invalid Filters: Providing invalid IDs or malformed filters may cause the API to reject the request.
  • Pagination Limits: When using auto pagination, setting an excessively high max pages value may lead to long execution times or rate limiting.
  • Empty Results: If no cards match the filters, the output will be an empty array; verify filter criteria if unexpected.

Links and References

Discussion