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 retrieving lists of support entries, searching by customer or content, creating and updating support records, analyzing support data, and uploading signatures for support entries.

The "Signatur hochladen" (Upload Signature) operation specifically uploads a signature for a given support entry identified by its Support-ID. This is useful in workflows where digital confirmation or approval of support tasks is required, for example, after completing a service call or appointment.

Practical examples:

  • Automatically upload a technician's signature after a support visit is completed.
  • Attach client approval signatures to support tickets for record-keeping.
  • Integrate signature capture into automated support workflows.

Properties

Name Meaning
API Token API token from TANSS authentication used to authorize requests.
Support-ID ID of the support entry for which the signature will be uploaded. Required for this operation.

Output

The node outputs JSON data representing the response from the TANSS API for the executed operation. For the "Signatur hochladen" operation, the output JSON typically contains confirmation details about the uploaded signature or the updated support entry.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the TANSS API.
  • Needs an API token credential for authentication.
  • The base URL for the TANSS API must be configured in the credentials.
  • Network access to the TANSS backend API endpoints.

Troubleshooting

  • Missing Credentials: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure that the API token credential is properly set up.
  • Invalid Support-ID: Operations requiring a Support-ID (like uploading a signature) will fail if the ID is missing or invalid.
  • Empty Fields: Creating or updating support entries without specifying required fields results in errors indicating missing data.
  • API Errors: Any HTTP or API errors during request execution are caught and reported with messages like "Fehler beim Ausführen von [operation]: [error message]". Check the API token validity, network connectivity, and input parameters.
  • Operation Not Recognized: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.

Links and References

Discussion