Actions8
Overview
The "TANSS Tickets" node manages ticket operations via the TANSS API. It supports creating, retrieving, updating, deleting, merging tickets, adding comments, searching tickets, and fetching ticket history including comments, support entries, and emails.
This node is useful in customer support or IT service management workflows where automated interaction with a ticketing system is needed. For example:
- Automatically creating tickets from incoming requests.
- Fetching ticket details or history to enrich data before further processing.
- Adding internal or public comments to tickets based on workflow events.
- Searching tickets by various criteria for reporting or automation.
- Merging duplicate tickets or deleting obsolete ones programmatically.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Ticket-ID | ID of the ticket to operate on (required for many operations). |
For the Ticket-Verlauf abrufen (Get Ticket History) operation specifically:
| Name | Meaning |
|---|---|
| API Token | API token for authentication |
| Ticket-ID | The ID of the ticket whose history is retrieved |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for the selected operation. For the "Ticket-Verlauf abrufen" operation, the output JSON contains the full history of the specified ticket, including comments, support entries, and emails related to that ticket.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- Needs network access to the configured TANSS API base URL.
- The node expects the API token to be provided as an input property.
- No additional external dependencies beyond the TANSS API.
Troubleshooting
- No credentials returned!: This error occurs if the node cannot retrieve the required API credentials. Ensure the API token credential is properly configured in n8n.
- Keine Felder für die Ticket-Erstellung angegeben.: When creating a ticket, at least one field must be provided. Make sure to fill in the required ticket creation fields.
- Keine Felder zum Aktualisieren angegeben.: When updating a ticket, at least one update field must be specified.
- Die Operation "XYZ" wird nicht erkannt.: Indicates an unsupported operation was selected. Verify the operation name is correct.
- Fehler beim Ausführen von XYZ: ...: General error during API request execution. Check the API token validity, network connectivity, and the correctness of input parameters like ticket IDs.
Links and References
- TANSS API Documentation (Replace with actual link if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices