Actions8
Overview
The "TANSS Tickets" node enables interaction with the TANSS ticket management API, allowing users to perform various operations on support tickets. This node is useful for automating ticket workflows such as searching for tickets based on criteria, creating new tickets, updating existing ones, adding comments, merging tickets, and deleting tickets.
Common scenarios include:
- Automatically retrieving tickets matching specific search filters (e.g., by status, priority, or assigned employee).
- Creating tickets from external systems or forms.
- Adding internal or public comments to tickets.
- Merging duplicate tickets into a single one.
- Updating ticket details programmatically.
- Deleting tickets with optional migration of related data.
Example: A support team could use this node to fetch all open tickets assigned to a particular employee created within the last week, then update their statuses or add comments automatically.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for all operations. |
| Suchkriterien | Collection of search criteria used only in the "Tickets suchen" operation, including: |
| - Suchtext | Text searched in ticket titles and descriptions. |
| - Unternehmen-ID | Filters tickets by company ID. |
| - Mitarbeiter-ID | Filters tickets by assigned employee ID. |
| - Status | Filters tickets by ticket status. |
| - Priorität | Filters tickets by ticket priority. |
| - Erstellt von (Datum) | Filters tickets created from this date (inclusive). |
| - Erstellt bis (Datum) | Filters tickets created up to this date (inclusive). |
Note: The above properties are specifically for the "Tickets suchen" operation.
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation performed:
- For "Tickets suchen", the output JSON contains the list of tickets matching the search criteria.
- For other operations like "createTicket", "getTicketById", "updateTicket", etc., the output JSON reflects the respective ticket data or confirmation responses.
- No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential for authentication.
- The node expects credentials configured in n8n that provide the base URL of the TANSS API and the API token.
- Uses standard HTTP methods (GET, POST, PUT, DELETE) to interact with the TANSS backend API.
Troubleshooting
No credentials returned!
Occurs if the node cannot retrieve the necessary API credentials. Ensure the API token and base URL are correctly configured in n8n credentials.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 fields under "Create Ticket 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 or misspelled operation name. Verify the selected operation is valid.Fehler beim Ausführen von [operation]: [error message]
Generic error during API request execution. Check network connectivity, API token validity, and that the requested resource exists.
Links and References
- TANSS API Documentation (not publicly linked here; refer to your organization's TANSS API docs)
- n8n HTTP Request Node documentation for understanding HTTP method usage: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/