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 create an annotation file on a card within a panel. This operation allows users to attach one or more file URLs as annotations to a specific card identified by its Card ID.
This node is beneficial in scenarios where you want to programmatically add file-based notes or references to cards in a project management or CRM-like panel system. For example, you might use it to attach documentation links, images, or other resources related to a task or contact represented by the card.
Practical example:
- Automatically attaching generated report URLs or screenshots to a task card after a workflow step completes.
- Adding reference files to a customer support ticket card for easier access by team members.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to which the annotation files will be attached. |
| File Urls | A collection of one or more URLs pointing to files to be added as annotations to the card. |
Output
The output of this operation is a JSON object representing the result returned by the API after creating the annotation file(s) on the specified card. This typically includes details about the created annotation such as IDs, URLs, timestamps, or status.
The node does not output binary data for this operation; it only returns JSON data describing the created annotation file entries.
Dependencies
- Requires an active connection to the WTS Chat API via an API key credential.
- The node uses the
WtsCrmService.createAnnotationFilemethod internally to perform the API call. - Proper permissions and valid Card ID are necessary to successfully create annotation files.
Troubleshooting
- Missing Card ID: If the Card ID is empty or not provided, the node throws an error indicating that the CardId field cannot be empty. Ensure you provide a valid Card ID.
- Invalid or unreachable File URLs: While the node accepts any URLs, if the URLs are invalid or inaccessible by the API backend, the creation may fail or the annotation may not be useful.
- API errors: Any issues from the API side (authentication failure, permission denied, rate limits) will be surfaced as errors. Check your API key validity and permissions.
- Empty File URLs collection: Providing an empty list of file URLs may cause unexpected behavior or errors. Always specify at least one URL.
Links and References
- WTS Chat API Documentation (general base URL referenced in code)
- Refer to your WTS Chat API docs for detailed schema and examples of annotation file creation endpoints.