Actions8
Overview
The "TANSS Tickets" node integrates with the TANSS API to manage ticket operations. It allows users to create, update, delete, search, and retrieve tickets and their associated comments or history within the TANSS system. This node is useful for automating customer support workflows, issue tracking, and ticket management directly from n8n.
Common scenarios include:
- Creating new support tickets automatically from incoming requests.
- Adding comments to existing tickets to log updates or internal notes.
- Searching tickets based on various criteria like status, priority, or assigned employee.
- Retrieving detailed ticket information or history for reporting or processing.
- Merging duplicate tickets or deleting resolved ones programmatically.
Example: Automatically create a ticket when a customer submits a form, then add internal comments as support agents update the case.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
Note: The user provided only the "API Token" property explicitly. However, the node supports many other properties depending on the selected operation:
| Name | Meaning |
|---|---|
| Operation | The action to perform on tickets. Options include: Create Ticket, Get Ticket by ID, Update Ticket, Delete Ticket, Create Comment, Get Ticket History, Search Tickets, Merge Tickets. |
| Ticket-ID | The ID of the ticket to operate on (required for most operations except searching and creating). |
| Search Criteria | Collection of filters for searching tickets, including search text, company ID, employee ID, status, priority, creation date range. |
| Target Ticket ID | For merging or deleting tickets, specifies the target ticket involved in the operation. |
| Comment Title | Title of the comment to add to a ticket. |
| Comment Content | Content/body of the comment. |
| Internal | Boolean flag indicating if the comment is internal (not visible to customers) or public. |
| Update Fields | Collection of fields to update on a ticket, such as company ID, title, content, status, due dates, etc. |
| Create Ticket Fields | Collection of fields required to create a new ticket, including company ID, title, content, assigned employee, status, priority, project flags, tags, and more. |
Output
The node outputs an array of JSON objects corresponding to the results of each input item processed. Each output object contains the raw JSON response returned by the TANSS API for the requested operation.
- For retrieval operations (e.g., getTicketById, getTicketHistory), the output includes detailed ticket data or history entries.
- For creation or update operations, the output contains the newly created or updated ticket or comment details.
- For search operations, the output includes a list of tickets matching the criteria.
- For delete and merge operations, the output reflects the success or failure status of the request.
The node does not output binary data.
Dependencies
- Requires access to the TANSS API endpoint, configured via credentials that provide the base URL and an API key/token.
- The user must supply a valid API token for authentication with the TANSS API.
- No additional external dependencies beyond standard HTTP request capabilities provided by n8n.
Troubleshooting
No credentials returned!
Occurs if the node cannot find the required API credentials. Ensure the TANSS API credentials are properly configured in n8n.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 creation fields.Keine Felder zum Aktualisieren angegeben. (No fields specified for updating)
When updating a ticket, specify at least one field to update.Die Operation "XYZ" wird nicht erkannt. (Operation not recognized)
Indicates an invalid or unsupported operation was selected. Verify the operation name is correct.Fehler beim Ausführen von XYZ: [error message] (Error executing XYZ)
General error during API call. Check the API token validity, network connectivity, and that the ticket IDs or parameters are correct.
Links and References
- TANSS API Documentation (not provided in code; consult your TANSS API provider for official docs)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/