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 emails, update ticket status as work progresses, 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 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 operate on (e.g., the ticket to be merged). |
| Target Ticket ID | ID of the target ticket where entities will be migrated or merged into (required for merging and deleting). |
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 details about the merge action, such as success status or updated ticket information.
No binary data output is produced by this node.
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 endpoints is necessary.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error "No credentials returned!" Ensure the API token is correctly set.
- Empty Required Fields: For operations like creating or updating tickets, if required fields are missing, errors like "Keine Felder für die Ticket-Erstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." appear. Provide all mandatory fields.
- Unrecognized Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls include the operation name and the original error message. Check network connectivity, API token validity, and correct parameter values.
- Invalid Ticket IDs: Using invalid or non-existent ticket IDs may cause API errors. Verify ticket IDs before running the node.
Links and References
- TANSS API Documentation (Replace with actual link if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.
This summary focuses on the "Tickets zusammenführen" operation within the "Default" resource context, highlighting relevant properties and behavior.