Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Get Panel By ID" operation in the WTS Chat node retrieves detailed information about a specific panel from the WTS API by its unique identifier. This operation is useful when you want to fetch comprehensive data about a particular panel, including optional related details such as cards, steps, tags, and other metadata associated with that panel.
Common scenarios include:
- Displaying or processing detailed panel information in workflows.
- Integrating panel data into dashboards or reports.
- Automating updates or actions based on panel contents.
For example, you might use this operation to get all cards and their statuses within a project management panel or to retrieve tags and steps associated with a sales pipeline panel.
Properties
| Name | Meaning |
|---|---|
| Panel ID | The unique identifier of the panel to retrieve. |
| Include Details | Optional additional details to include in the response. Possible values: Cards, Steps, StepsCardCount, StepsFields, Tags |
Output
The output is a JSON object containing the panel's data as returned by the WTS API. This includes the core panel information and any optionally included details specified by the user (such as cards, steps, tags, etc.).
The structure typically contains:
- Basic panel attributes (e.g., id, title, description).
- Nested arrays or objects for included details like cards, steps, counts, fields, and tags depending on the selected options.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the WTS API via an API key credential.
- The node uses the WTS CRM service internally to fetch panel data.
- Network access to
https://api.wts.chatis necessary.
Troubleshooting
- Missing Panel ID: If the "Panel ID" property is empty, the node throws an error prompting to fill in the panel ID field.
- API Errors: Any issues communicating with the WTS API (e.g., invalid API key, network errors) will result in an error wrapped as a NodeApiError.
- Invalid Include Details Options: Selecting unsupported or malformed options in "Include Details" may cause unexpected results or errors.
- Rate Limits: If many requests are made rapidly, the API might throttle requests; consider adding delays between executions if processing multiple panels.
Links and References
- WTS API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes (for understanding node development concepts)