Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node interacts with the "Panel" resource of the WTS Chat API, specifically supporting the operation to retrieve all panels ("Get All Panels"). It fetches a list of panels filtered and sorted according to user-defined criteria. This is useful in scenarios where you want to automate workflows involving panel data management, such as monitoring available panels, integrating panel information into other systems, or triggering actions based on panel attributes.
For example, you might use this node to:
- Retrieve all panels with a specific title or created within a certain date range.
- Automatically paginate through large sets of panels to process or analyze them.
- Sort panels by creation or update dates in ascending or descending order.
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 fetch when auto pagination is enabled (range: 1 to 100). |
| Page Number | The page number to retrieve when auto pagination is disabled (default: 1). |
| Page Size | Number of items per page when auto pagination is disabled (range: 1 to 100, default: 15). |
| Order By | Field name to sort the results by (e.g., creation date, update date). |
| Order Direction | Sorting direction: "Ascending" or "Descending". |
Output
The output is an array of JSON objects, each representing a panel retrieved from the WTS Chat API. Each object contains the panel's details as returned by the API, which typically includes fields like panel ID, title, creation and update timestamps, and possibly additional metadata depending on the API response.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the WTS Chat API via an API key credential.
- The node uses the WTS Chat API base URL
https://api.wts.chat. - Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Empty or missing API key: Ensure that the API key credential is correctly set up and linked to the node.
- Invalid date formats: Date/time filters must follow the format
YYYY-MM-DD hh:mmand respect the time zone; otherwise, the API may reject the request. - Pagination issues: If auto pagination is enabled but no results are returned beyond the first page, verify the
Max Pagessetting and API limits. - API errors: Errors thrown by the API will be surfaced as node errors. Check the error message for details, such as invalid parameters or permission issues.
- Missing required parameters: Although most filters are optional, ensure that any mandatory parameters for your use case are provided.
Links and References
- WTS Chat API Documentation (general reference for API endpoints and parameters)
- n8n Documentation (for configuring credentials and using nodes)
This summary is based solely on static analysis of the provided source code and property definitions.