TANSS Support

Verwaltet Support-Einträge und Termine in der TANSS API
Join our community

Actions9

Overview

This node integrates with the TANSS API to manage support entries and appointments. It allows users to perform various operations such as searching, listing, creating, updating, analyzing, and uploading signatures related to support records. A common use case is automating support ticket management or retrieving filtered support data for reporting or further processing.

For the selected operation "Support nach Inhalt suchen" (Search support by content), the node searches support entries based on a text string found in their descriptions. This is useful when you want to find all support tickets or entries that mention specific keywords or phrases in their description fields.

Example scenario:
You want to find all support cases where the description contains the word "network outage" to analyze recurring issues or prepare reports.

Properties

Name Meaning
API Token API token from the TANSS authentication used to authorize requests to the TANSS API.
Suchtext Text string to search within support descriptions. The node returns support entries containing this text.

Output

The node outputs an array of JSON objects representing the support entries matching the search criteria. Each item corresponds to one support record returned by the TANSS API. The exact structure depends on the API response but typically includes details like support ID, description, dates, customer info, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the TANSS API.
  • Needs an API token credential configured in n8n for authentication.
  • The base URL for the TANSS API must be set in the credentials.
  • The node uses HTTP requests to communicate with the API endpoints.

Troubleshooting

  • Missing API Token: If no API token is provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token credential is correctly set.
  • Empty Search Text: If the search text is empty, the node throws "Suchtext ist erforderlich." (Search text is required). Provide a valid non-empty string.
  • API Request Errors: Network issues or invalid tokens may cause request failures. The node will report errors like Fehler beim Ausführen von searchByContent: <error message>. Verify network connectivity and token validity.
  • Unexpected Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.

Links and References

Discussion