Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
This node integrates with the WTS Chat API to manage "Panel" resources, specifically allowing users to create annotation files linked to cards within a panel. The "Create Annotation File" operation lets you attach one or more file URLs as annotations to a specified card.
Typical use cases include:
- Adding external document references or media files as annotations to project management cards.
- Attaching supporting files (e.g., images, PDFs) to tasks or items tracked in a panel system.
- Automating the enrichment of card data with relevant file links for team collaboration.
Example: Automatically add a list of image URLs as annotations to a task card when triggered by an event.
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 node outputs JSON data representing the response from the API after creating the annotation file(s). This typically includes details about the newly created annotation such as IDs, associated card information, and the list of file URLs attached.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WTS Chat API.
- The node uses the
WtsCrmService.createAnnotationFilemethod internally to perform the API call. - No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Missing Card ID: If the "Card ID" property is empty, the node throws an error indicating that the CardId cannot be empty. Ensure this field is filled with a valid card identifier.
- Invalid or Empty File URLs: If no file URLs are provided, the API may reject the request or return an error. Make sure to provide at least one valid URL in the "File Urls" collection.
- API Authentication Errors: If the API key credential is missing or invalid, the node will fail with authentication errors. Verify that the API key is correctly configured in n8n credentials.
- Network or API Errors: Any other errors returned by the API are wrapped and thrown as node errors. Check the error message for details and verify network connectivity and API status.
Links and References
- WTS Chat API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes
- Best practices for handling file URLs and annotations in project management tools