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 criteria (e.g., by status, priority, or assigned employee).
- Creating new support tickets from external systems or forms.
- Adding internal or public comments to tickets as part of a workflow.
- Updating ticket details programmatically.
- Merging duplicate tickets or deleting obsolete ones.
For example, a customer 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 based on automated analysis.
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: |
| - Suchtext | Text to search within ticket titles and descriptions. |
| - Unternehmen-ID | Filter tickets by company ID. |
| - Mitarbeiter-ID | Filter tickets by assigned employee ID. |
| - Status | Filter tickets by ticket status. |
| - Priorität | Filter tickets by ticket priority. |
| - Erstellt von (Datum) | Filter tickets created from this date (inclusive). |
| - Erstellt bis (Datum) | Filter tickets created up to this date (inclusive). |
Note: The above properties are specifically for the "Tickets suchen" (search tickets) operation.
Output
The node outputs an array of JSON objects representing the response from the TANSS API for the selected 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.
- Network access to the TANSS API server must be available from the n8n instance.
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's credentials section.Keine Felder für die Ticket-Erstellung angegeben. (No fields specified for ticket creation)
When creating a ticket, at least one field must be provided. Make sure to fill in the required ticket fields.Keine Felder zum Aktualisieren angegeben. (No fields specified for update)
When updating a ticket, specify at least one field to update.Die Operation "XYZ" wird nicht erkannt. (Operation not recognized)
This indicates an unsupported or misspelled operation name. Verify the operation selection.Fehler beim Ausführen von [operation]: [error message]
General error during API request execution. Check network connectivity, API token validity, and correctness of input parameters.
Links and References
- TANSS API Documentation (not publicly linked here; refer to your organization's TANSS API docs)
- n8n Documentation: Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node