Actions8
Overview
This node integrates with the TANSS ticketing system API to manage tickets and their related data. Specifically, the "Kommentar erstellen" (Create Comment) operation allows users to add comments to existing tickets within TANSS. This is useful for support teams or project managers who want to document updates, internal notes, or public remarks on a ticket.
Typical use cases include:
- Adding progress updates or clarifications to a support ticket.
- Recording internal discussions or instructions that should not be visible to customers.
- Attaching additional information or context to a ticket after it has been created.
For example, a support agent can use this node to append a comment titled "Customer Follow-up" with content describing recent communications, marking it as internal so it remains confidential within the team.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests. |
| Ticket-ID | The unique identifier of the ticket to which the comment will be added. |
| Comment Title | The title or subject line of the comment being created. |
| Comment Content | The main text content of the comment. |
| Internal | Boolean flag indicating if the comment is internal (true) or public (false). |
Output
The node outputs JSON data representing the response from the TANSS API after creating the comment. This typically includes details about the newly created comment such as its ID, title, content, visibility status (internal/public), timestamps, and possibly metadata about the author or ticket association.
No binary data output is produced by this operation.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network access to the TANSS backend API endpoint is necessary.
Troubleshooting
- Missing or invalid API token: The node will throw an error if the API token is missing or incorrect. Ensure the token is correctly entered and has sufficient permissions.
- Invalid Ticket-ID: If the specified ticket does not exist or the ID is incorrect, the API may return an error. Verify the ticket ID before running the node.
- Empty comment fields: The node requires both a comment title and content. Omitting these may cause errors or result in empty comments.
- API request failures: Network issues or server errors from the TANSS API will cause the node to fail with an error message indicating the operation and the underlying issue.
- Permission issues: If the API token lacks rights to add comments, the operation will fail. Confirm user permissions in TANSS.
Links and References
- TANSS API Documentation (Replace with actual link if available)
- n8n Documentation: Creating Custom Nodes
- General REST API concepts: REST API Tutorial