Actions8
Overview
The node "TANSS Tickets" manages ticket operations via the TANSS API. It allows users to perform various actions on tickets such as updating, creating comments, retrieving details, searching, merging, and deleting tickets. This node is beneficial in scenarios where you want to automate or integrate ticket management workflows within the TANSS system, for example:
- Automatically updating ticket details based on external triggers.
- Adding comments to tickets programmatically.
- Searching tickets with specific criteria to generate reports or trigger further actions.
- Merging duplicate tickets or cleaning up old tickets.
Specifically, the "Ticket aktualisieren" (Update Ticket) operation updates an existing ticket with new information provided by the user.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Ticket-ID | The ID of the ticket to update. |
| Update Fields | Collection of fields to update on the ticket. These include: |
| - Company ID (number) | |
| - Remitter ID (number) | |
| - Title (string) | |
| - Content (string) | |
| - External Ticket ID (string) | |
| - Assigned to Employee ID (number) | |
| - Assigned to Department ID (number) | |
| - Status ID (number) | |
| - Type ID (number) | |
| - Deadline Date (timestamp as number) | |
| - Due Date (timestamp as number) | |
| - Attention (options): No, Yes, Resubmission, Mail | |
| - Installation Fee (options): No, Yes, No Project Installation Fee | |
| - Relationship Link Type ID (number) | |
| - Relationship Link ID (number) | |
| - Resubmission Date (timestamp as number) | |
| - Estimated Minutes (number) | |
| - Phase ID (number) | |
| - Order Number (string) |
Output
The output is a JSON object representing the response from the TANSS API after attempting to update the ticket. This typically includes the updated ticket data or confirmation of the update operation. The structure depends on the TANSS API response but generally contains ticket properties reflecting the new state.
No binary data output is produced by this operation.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node uses the base URL from the credentials to construct API endpoints.
- Network access to the TANSS backend API is necessary.
- Proper configuration of the API token in the node's input properties is mandatory.
Troubleshooting
Error: "Keine Felder für die Ticket-Erstellung angegeben."
This error occurs if no fields are provided when trying to create a ticket. For updating, a similar check ensures at least one field is specified. Make sure to provide at least one field in "Update Fields".Error: "Fehler beim Ausführen von updateTicket: ..."
Indicates an issue during the API request. Common causes include invalid API token, incorrect ticket ID, or network issues. Verify the API token validity, ticket existence, and network connectivity.Error: "Die Operation 'updateTicket' wird nicht erkannt."
Means the operation name is not recognized. Ensure the operation property is correctly set to "updateTicket".If the API token is missing or invalid, the node will throw an error indicating no credentials returned or authorization failure.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider for official docs)
- n8n Documentation on Creating Custom Nodes
- General REST API usage and error handling best practices