TANSS Tickets icon

TANSS Tickets

Verwaltet Ticket-Operationen in der TANSS API

Actions8

Overview

This node integrates with the TANSS ticket management API to perform various operations on support tickets. It allows users to create, update, delete, merge tickets, add comments, retrieve ticket details by ID, fetch the ticket history (including comments, support entries, and emails), and search tickets based on multiple criteria.

Common scenarios where this node is beneficial include automating customer support workflows, synchronizing ticket data between systems, or building custom dashboards that interact with TANSS tickets programmatically.

For example:

  • Automatically creating a new ticket when a customer submits a form.
  • Fetching the full history of a ticket to display in a CRM.
  • Adding internal or public comments to a ticket as part of an automated process.
  • Searching for tickets assigned to a specific employee or within a date range.

Properties

Name Meaning
API Token API token from TANSS authentication used to authorize requests.
Ticket-ID The unique identifier of the ticket to operate on (required for most operations).

Operation: Ticket-Verlauf abrufen (Get Ticket History)

  • Operation: Fixed to "getTicketHistory" for this context.
  • API Token: Required string input, the authentication token.
  • Ticket-ID: Number input specifying which ticket's history to retrieve.

Output

The node outputs an array of JSON objects representing the response from the TANSS API for the requested 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.

Example output structure (simplified):

{
  "ticketId": 123,
  "history": [
    {
      "type": "comment",
      "author": "User A",
      "content": "Initial issue description",
      "timestamp": "2024-01-01T12:00:00Z"
    },
    {
      "type": "supportEntry",
      "details": "...",
      "timestamp": "2024-01-02T08:30:00Z"
    },
    {
      "type": "email",
      "subject": "Re: Issue update",
      "body": "...",
      "timestamp": "2024-01-03T09:15:00Z"
    }
  ]
}

Dependencies

  • Requires an active TANSS API endpoint URL configured in credentials.
  • Requires an API token credential for authenticating requests.
  • Uses HTTP requests with JSON payloads to communicate with the TANSS backend API.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot find the required API token credential. Ensure the API token is correctly set up in the node credentials.

  • Keine Felder für die Ticket-Erstellung angegeben. (No fields provided for ticket creation)
    When creating a ticket, you must provide at least one field in the "createTicketFields" property.

  • Keine Felder zum Aktualisieren angegeben. (No fields provided for updating)
    When updating a ticket, at least one field must be specified in the "updateFields" property.

  • Die Operation "XYZ" wird nicht erkannt. (The operation "XYZ" is not recognized)
    This indicates an unsupported operation was selected. Verify the operation name is valid.

  • Fehler beim Ausführen von [operation]: [error message]
    General error during API request execution. Check the API token validity, network connectivity, and that the ticket ID exists.

Links and References

Discussion