TANSS Tickets icon

TANSS Tickets

Verwaltet Ticket-Operationen in der TANSS API
Join our community

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 for authenticating API calls.
  • 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 and a valid API token credential for authentication.
  • The node expects the base URL of the TANSS API to be configured in the credentials.
  • No additional external libraries beyond standard n8n workflow helpers are required.

Troubleshooting

  • Error: "No credentials returned!"
    This indicates that the API token credential was not provided or could not be retrieved. Ensure the API token is correctly set up in the node credentials.

  • Error: "Fehler beim Ausführen von getTicketHistory: ..."
    This error occurs if the API request fails. Common causes include invalid ticket ID, expired or incorrect API token, or network issues. Verify the ticket ID exists and the API token is valid.

  • Empty or missing ticket history
    If the ticket has no recorded history, the output may be empty. Confirm the ticket ID is correct and that there is historical data available in TANSS.

Links and References

Discussion