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 operations related to annotation cards on panels. The Delete Annotation Card operation allows users to delete a specific annotation (note) from a card within a panel by providing the card ID and the note ID.
This operation is useful in scenarios where you want to programmatically manage annotations on project or task cards, such as removing outdated comments or files attached as annotations. For example, if a team member adds an incorrect note to a card, this node can be used to remove that note automatically.
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. |
Note: The provided properties JSON only included cardId for some operations but the code shows that for deleting an annotation card, both cardId and noteId are required input parameters.
Output
The output of this operation is a JSON object representing the response from the API after deleting the annotation card. It typically contains confirmation details about the deletion or the updated state of the card's annotations.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WTS Chat API.
- The base URL for API requests is
https://api.wts.chat. - The node depends on internal service classes (
WtsCrmService) to perform the API call for deleting the annotation card.
Troubleshooting
Missing Card ID or Note ID: If either the Card ID or Note ID is not provided, the node throws an error:
"Fill in NoteId and CardId" — Ensure both fields are filled before execution.API Errors: Any errors returned by the WTS Chat API during the deletion process are caught and rethrown as node errors. Common issues might include invalid IDs or insufficient permissions.
Network Issues: Connectivity problems with the API endpoint may cause failures; verify network access and API availability.
Links and References
- WTS Chat API Documentation (general reference, actual docs URL may vary)
- n8n documentation on Creating Custom Nodes
If you need further details on other operations or resources, feel free to ask!