Actions8
Overview
The "TANSS Tickets" node enables interaction with the TANSS API to manage support tickets. It supports multiple operations such as creating, updating, deleting tickets, adding comments, retrieving ticket details and history, merging tickets, and searching tickets based on various criteria.
This node is beneficial in scenarios where you want to automate or integrate your ticket management workflow within n8n, for example:
- Automatically creating tickets from incoming customer requests.
- Searching and filtering tickets to generate reports or trigger follow-up actions.
- Adding internal or public comments to tickets programmatically.
- Merging duplicate tickets or cleaning up old tickets.
- Retrieving ticket histories for audit or analysis purposes.
Practical example: You could use this node to search for all open tickets assigned to a specific employee created within the last month, then update their status or notify the responsible team automatically.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for all operations. |
| Suchtext | Text to search within ticket titles and descriptions (searchTickets operation). |
| Unternehmen-ID | Filter tickets by company ID (searchTickets operation). |
| Mitarbeiter-ID | Filter tickets by assigned employee ID (searchTickets operation). |
| Status | Filter tickets by ticket status (searchTickets operation). |
| Priorität | Filter tickets by priority (searchTickets operation). |
| Erstellt von | Filter tickets created from this date/time (searchTickets operation). |
| Erstellt bis | Filter tickets created until this date/time (searchTickets operation). |
Note: The above properties relate specifically to the "Tickets suchen" (searchTickets) operation.
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each executed operation. For the "Tickets suchen" operation, the output JSON contains the list of tickets matching the specified search criteria, including their details such as IDs, titles, statuses, priorities, assigned employees, creation dates, and other relevant ticket metadata.
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 the TANSS API base URL to be provided via credentials configuration.
- No additional external dependencies beyond the TANSS API and n8n's HTTP request helper.
Troubleshooting
No credentials returned!
This error occurs if the node cannot retrieve the necessary API token credential. Ensure that the API token is correctly configured in the node 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 ticket fields before execution.Keine Felder zum Aktualisieren angegeben.
When updating a ticket, specify at least one field to update; otherwise, the operation will fail.Die Operation "XYZ" wird nicht erkannt.
Indicates an unsupported or misspelled operation name. Verify that the selected operation is valid.Fehler beim Ausführen von [operation]: [error message]
General error during API call. Check the API token validity, network connectivity, and that the parameters are correct.
Links and References
- TANSS API Documentation (not publicly linked here; refer to your internal TANSS API docs)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- n8n Credentials Management: https://docs.n8n.io/credentials/overview/