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). |
Output
The node outputs JSON data representing the response from the TANSS API for the executed operation. For the "mergeTickets" operation, this typically includes confirmation of the merge action and details about the resulting ticket state.
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 that provide the base URL for the TANSS API and the API token.
- Network access to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If no credentials are returned, the node throws an error. Ensure the API token credential is properly set up in n8n.
- Empty Fields for Creation/Update: When creating or updating tickets, if no fields are provided, the node raises an error. Always specify required fields.
- Invalid 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 ticket IDs.
- Merge Operation Specific: Ensure both source and target ticket IDs are valid and exist; otherwise, the merge will fail.
Links and References
- TANSS API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices