Actions8
Overview
The "TANSS Tickets" node manages ticket operations via the TANSS API. It supports creating, updating, deleting, retrieving, searching, commenting on, and merging tickets within the TANSS system. This node is useful for automating customer support workflows, integrating ticket management into broader automation processes, or synchronizing ticket data with other systems.
A practical example: Automatically create a new ticket when a customer submits a form, add comments based on follow-up interactions, and merge duplicate tickets to keep the system clean.
For the selected operation "Tickets zusammenführen" (mergeTickets), the node merges one ticket into another, consolidating their information under a single target ticket ID.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Ticket-ID | ID of the source ticket to be merged (the ticket that will be merged into the target). |
| Target Ticket ID | ID of the target ticket where the source ticket's data will be merged into. |
Output
The node outputs JSON data representing the response from the TANSS API for the performed operation. For the "mergeTickets" operation, this typically includes confirmation of the merge action and details about the updated target ticket.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential.
- The node expects credentials configured in n8n containing the base URL of the TANSS API.
- Network access to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If no API credentials are provided, the node throws an error "No credentials returned!" Ensure the API token and base URL are correctly configured.
- Empty Fields for Merge: If required fields like Ticket-ID or Target Ticket ID are missing or zero, the API call may fail or behave unexpectedly. Always provide valid numeric IDs.
- Unrecognized Operation: If an unsupported operation value is set, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during HTTP requests return messages like "Fehler beim Ausführen von mergeTickets: [error message]". Check network connectivity, API token validity, and correct ticket IDs.
- Permission Issues: Insufficient permissions in the TANSS system can cause failures; verify the API token has rights to merge tickets.
Links and References
- TANSS API Documentation (refer to your internal or vendor-provided docs for detailed API endpoints and payloads)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API best practices for error handling and authentication