Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
This node interacts with the "Panel" resource of the WTS Chat API, specifically supporting the operation Get Card By ID. It retrieves detailed information about a specific card within a panel by its unique identifier. This is useful in scenarios where you need to fetch comprehensive data about a particular card for further processing, reporting, or integration with other systems.
Practical examples include:
- Fetching a card's details to display in a dashboard.
- Retrieving card metadata and custom fields for automation workflows.
- Accessing related entities like contacts or responsible users linked to the card.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to retrieve. |
| Include Details | Optional additional details to include in the response. Possible values: Contacts, CustomFields, PanelTitle, ResponsibleUser, StepPhase, StepTitle |
Output
The output is a JSON object representing the card data retrieved from the API. It includes all standard card properties such as title, description, position, monetary amount, tags, and optionally expanded details depending on the "Include Details" property. The exact structure depends on the API response but typically contains:
- Basic card attributes (ID, title, description, etc.)
- Related entities if requested (e.g., contacts linked to the card)
- Custom fields and metadata associated with the card
- Status and positional information within the panel
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the WTS Chat API via an API key credential.
- The node uses the
WtsCrmService.getCardByIdmethod internally to fetch card data. - Proper configuration of the API base URL and authentication credentials in n8n is necessary.
Troubleshooting
Error: "CardID is empty, please fill it in"
Occurs if the Card ID property is not provided or left blank. Ensure that the Card ID field is filled with a valid identifier.API Errors / Network Issues
If the API key is invalid or network connectivity issues occur, the node will throw errors. Verify API credentials and network access.Invalid Include Details Options
Providing unsupported options in the "Include Details" multi-select may cause unexpected results or partial data. Use only the documented options.
Links and References
- WTS Chat API Documentation (Assumed official docs URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General info on Working with APIs in n8n