Actions38
- 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 to delete an annotation card from a panel. The node allows users to remove a specific annotation (note) identified by its Note ID from a card identified by its Card ID within a panel.
Common scenarios where this node is useful include:
- Managing project or task boards where annotation cards represent comments or notes on tasks.
- Automating cleanup or archival processes by programmatically deleting outdated or irrelevant annotations.
- Integrating with other workflow steps that modify panel cards and require removing certain annotations as part of the process.
Example use case:
- A user wants to automatically delete a comment (annotation) from a task card in a project management panel when the task is completed or no longer relevant.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card from which the annotation (note) will be deleted. |
| Note ID | The unique identifier of the annotation (note) to delete from the specified card. |
Output
The output of this operation is a JSON object representing the result of the deletion request. Typically, this would confirm whether the annotation was successfully deleted or provide details about the deleted annotation.
The json output field contains the response from the API call to delete the annotation card.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WTS Chat API.
- Requires an API key credential for authentication with the WTS Chat service.
- The node uses the
WtsCrmService.deleteAnnotationCardmethod internally to perform the deletion via the API.
Troubleshooting
- Missing Card ID or Note ID: The node throws an error if either the Card ID or Note ID is not provided. Ensure both fields are filled before execution.
- Invalid IDs: If the provided Card ID or Note ID does not exist or is invalid, the API may return an error. Verify the correctness of these IDs.
- API Authentication Errors: If the API key credential is missing or invalid, the node will fail to authenticate. Check the API key configuration.
- Network Issues: Connectivity problems with the WTS Chat API endpoint can cause failures. Confirm network access and API availability.
Common error messages:
"Fill in NoteId and CardId": Indicates one or both required parameters are missing.- API errors wrapped as
NodeApiErrorwith messages from the WTS Chat API indicating issues like authorization failure, resource not found, or invalid input.
Links and References
- WTS Chat API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes (for understanding node development concepts)