Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The WTS Chat - Panel: Get All Cards operation retrieves a list of cards from a specified panel in the WTS system. This is useful for automating workflows that need to process, filter, or analyze cards (such as tasks, deals, or tickets) managed within panels. Common scenarios include syncing card data with other systems, generating reports, or triggering actions based on card status.
Practical examples:
- Fetch all sales opportunities from a specific pipeline stage for reporting.
- List all support tickets assigned to a particular user.
- Retrieve cards containing a certain keyword for further processing.
Properties
Below are the input properties relevant to the Panel → Get All Cards operation:
| Display Name | Type | Description |
|---|---|---|
| Responsible Name or ID | options | Choose the responsible user for the cards, or specify an ID using an expression. |
| Contact ID | string | Filter cards by associated contact ID. |
| Panel Name or ID | options | Select the panel to retrieve cards from, or specify its ID via an expression. |
| Step Name or ID | options | Filter cards by step/stage within the selected panel. |
| Text Filter | string | Filter cards by text content (e.g., title or description). |
| Include Archived | boolean | Whether to include archived cards in the results. |
| Include Details | multiOptions | Specify which additional details to include (Contacts, CustomFields, PanelTitle, etc.). |
| CreatedAt.After | dateTime | Only include cards created after this date/time. |
| CreatedAt.Before | dateTime | Only include cards created before this date/time. |
| UpdatedAt.After | dateTime | Only include cards updated after this date/time. |
| UpdatedAt.Before | dateTime | Only include cards updated before this date/time. |
| Auto Pagination | boolean | Enable automatic pagination to fetch multiple pages of results. |
| Max Pages | number | Maximum number of pages to retrieve (used if auto pagination is enabled). |
| Page Number | number | The page number to retrieve (used if auto pagination is disabled). |
| Page Size | number | Number of items per page (used if auto pagination is disabled). |
| Order By | string | Field name to sort the results by. |
| Order Direction | options | Sort direction: Ascending or Descending. |
Output
The node outputs an array of objects under the json field. Each object represents a card retrieved from the specified panel. The structure of each card object depends on the "Include Details" options selected, but typically includes:
{
"id": "string",
"title": "string",
"description": "string",
"panelId": "string",
"stepId": "string",
"responsibleUserId": "string",
"contactIds": ["string"],
"monetaryAmount": "number",
"archived": "boolean",
"createdAt": "string (ISO date)",
"updatedAt": "string (ISO date)",
// ...additional fields depending on 'Include Details' selection
}
- If "Include Details" is used, extra fields such as contacts, custom fields, panel/step titles, and responsible user info may be present.
- The output does not contain binary data.
Dependencies
- External Service: Requires access to the WTS API.
- API Key: You must configure valid WTS API credentials (
wtsApi) in n8n. - Environment: No special environment variables required beyond standard n8n credential setup.
Troubleshooting
Common Issues:
Missing Required Fields:
- If "Panel Name or ID" is not provided or set to "Undefined", the node will throw an error:
"Fill in the panel ID field" - Solution: Ensure you select a valid panel.
- If "Panel Name or ID" is not provided or set to "Undefined", the node will throw an error:
Invalid Filters:
- Providing invalid IDs or filter values may result in empty results or API errors.
Pagination Limits:
- If "Auto Pagination" is enabled but "Max Pages" is too low, you might not get all available cards.
- Solution: Increase "Max Pages" or adjust filters.
API Authentication Errors:
- If your API key is missing or incorrect, authentication errors will occur.
- Solution: Check your n8n credentials configuration.