Actions8
Overview
This node integrates with the TANSS ticketing system API to manage tickets and their related data. Specifically, for the "Kommentar erstellen" (Create Comment) operation, it allows users to add comments to existing tickets within TANSS. This is useful in scenarios where support agents or team members want to document updates, provide additional information, or communicate internally about a specific ticket.
Practical examples:
- Adding a public comment to inform a customer about progress.
- Adding an internal note visible only to support staff.
- Documenting troubleshooting steps or decisions made during ticket resolution.
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 content/body text 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 of the newly created comment such as its ID, title, content, visibility (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 endpoint URL configured in credentials.
- Requires a valid API token credential for authenticating requests.
- The node uses HTTP requests to interact with the TANSS backend API.
Troubleshooting
- Missing or invalid API token: The node requires a valid API token; ensure the token is correctly provided and has necessary permissions.
- Invalid Ticket-ID: If the ticket ID does not exist or is incorrect, the API will return an error. Verify the ticket ID before running.
- Empty comment fields: Both comment title and content should be provided; empty values may cause the API to reject the request.
- API errors: Errors returned from the TANSS API are surfaced with messages like
Fehler beim Ausführen von createComment: <error message>. Check the error message for details and verify network connectivity and API status. - Credential issues: If no credentials are returned, the node throws an error. Ensure credentials are properly set up in n8n.
Links and References
- TANSS API documentation (not publicly linked here; refer to your organization's TANSS API docs)
- n8n HTTP Request node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/