Actions8
Overview
The "TANSS Tickets" node manages ticket operations via the TANSS API. It supports creating, updating, deleting, retrieving, searching, merging tickets, and adding comments to tickets. This node is useful for automating customer support workflows, integrating ticket management into broader automation processes, or synchronizing ticket data with other systems.
Practical examples:
- Automatically create a new support ticket when a customer submits a form.
- Retrieve ticket details by ID to display in a dashboard.
- Add internal or public comments to tickets based on workflow events.
- Delete or merge tickets as part of cleanup or consolidation tasks.
- Search tickets by criteria such as status, priority, or assigned employee.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Ticket-ID | The ID of the ticket to operate on (required for many operations). |
| Target Ticket ID | ID of the target ticket for migrating or merging entities (used in delete and merge). |
For the "Ticket löschen" (delete ticket) operation specifically, the relevant properties are:
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication. |
| Ticket-ID | ID of the ticket to be deleted. |
| Target Ticket ID | Optional ID of another ticket to which entities should be migrated during deletion. |
Output
The node outputs JSON data representing the response from the TANSS API for the performed operation. For the "Ticket löschen" operation, the output JSON typically contains confirmation of the deletion or details about the affected tickets.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL configured in credentials.
- Requires an API token credential for authenticating requests.
- Uses HTTP methods (GET, POST, PUT, DELETE) to interact with the TANSS backend API.
Troubleshooting
- Missing Credentials: If no API token or base URL is provided, the node will throw an error indicating missing credentials.
- Empty Required Fields: For operations like ticket creation or update, if required fields are empty, the node throws an error specifying that no fields were provided.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Network issues or invalid tokens can cause request failures; errors include the operation name and the original error message for easier debugging.
- Target Ticket ID Usage: When deleting a ticket with migration, ensure the target ticket ID is valid; otherwise, the API may reject the request.
Links and References
- TANSS API Documentation (not provided here, but users should consult their official API docs)
- n8n HTTP Request Node documentation for understanding underlying request mechanics
This summary focuses on the "Ticket löschen" operation within the "Default" resource context, describing its inputs, outputs, and behavior based on static code analysis.