Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Get All Panels" operation of the WTS Chat node retrieves a list of panels from the WTS API. Panels are likely organizational or workflow entities used to group or manage cards and annotations within the system. This operation supports filtering by title and date ranges, sorting, and pagination.
This node operation is beneficial when you want to programmatically fetch all panels for reporting, synchronization, or automation purposes. For example, you might use it to:
- Retrieve all panels created or updated within a specific timeframe.
- List panels sorted by creation date or title.
- Automatically paginate through large numbers of panels to process them in batches.
Properties
| Name | Meaning |
|---|---|
| Title | Filter panels by their title (string match). |
| CreatedAt.After | Filter panels created after this date/time (format: YYYY-MM-DD hh:mm, timezone-aware). |
| CreatedAt.Before | Filter panels created before this date/time (format: YYYY-MM-DD hh:mm, timezone-aware). |
| UpdatedAt.After | Filter panels updated after this date/time (format: YYYY-MM-DD hh:mm, timezone-aware). |
| UpdatedAt.Before | Filter panels updated before this date/time (format: YYYY-MM-DD hh:mm, timezone-aware). |
| Auto Pagination | Boolean flag to enable automatic pagination, fetching multiple pages automatically. |
| 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 (starting at 1). |
| Page Size | Number of items per page when auto pagination is disabled (1 to 100). |
| Order By | Field name to sort the results by (e.g., creation date, title). |
| Order Direction | Direction of sorting: Ascending or Descending. |
Output
The output is an array of JSON objects representing panels retrieved from the WTS API. Each item corresponds to a panel entity with its properties as returned by the API. The exact structure depends on the API response but typically includes fields such as panel ID, title, creation and update timestamps, and possibly metadata or custom fields.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the WTS API.
- The node uses the base URL
https://api.wts.chatfor API requests. - No additional external services are required beyond the WTS API.
Troubleshooting
- Empty or missing panel ID: If you attempt to get a panel by ID without providing the ID, the node throws an error prompting to fill in the panel ID field.
- API authentication errors: Ensure that the API key credential is correctly configured and valid.
- Invalid date formats: Date filters must be provided in the format
YYYY-MM-DD hh:mmand respect your time zone. - Pagination issues: When using auto pagination, setting an excessively high max pages value may lead to long execution times or rate limiting.
- Network or API errors: Any network failures or API errors will be surfaced as node errors with messages from the API.
Links and References
- WTS Chat API Documentation (Assumed, please replace with actual link if available)
- n8n Documentation on Creating Custom Nodes
- General info on Pagination in APIs