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 associated with a given support entry ID. This is useful in scenarios where a digital signature needs to be attached to confirm or validate a support service, for example, after a technician completes a service call.

Practical examples:

  • Automatically upload a customer's signature after a support visit is completed.
  • Attach signed confirmations to support tickets for audit or compliance purposes.

Properties

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

Note: These properties are relevant for the "Signatur hochladen" operation.

Output

The node outputs JSON data representing the response from the TANSS API after uploading the signature. The exact structure depends on the API's response but generally includes confirmation or details about the uploaded signature.

No binary data output is involved in this operation.

Example output JSON structure (illustrative):

{
  "success": true,
  "message": "Signature uploaded successfully",
  "supportId": 12345
}

Dependencies

  • Requires an active TANSS API credential with a valid base URL and API token.
  • The node expects the API token to be provided as an input property.
  • Network access to the configured TANSS API endpoint is necessary.

Troubleshooting

  • Missing Credentials: If no credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure that the API credential is properly configured in n8n.
  • Invalid Support-ID: Providing an invalid or zero support ID may cause the API request to fail. Always specify a valid support entry ID.
  • API Errors: Any errors returned by the TANSS API during the upload will be caught and rethrown with a message like "Fehler beim Ausführen von uploadSignature: [error message]". Check the API token validity and network connectivity.
  • Empty Body: Although the uploadSignature operation sends an empty body, ensure the support ID is correctly set; otherwise, the API might reject the request.

Links and References

  • TANSS API Documentation (not provided here, but refer to your internal TANSS API docs)
  • n8n Documentation: Creating Custom Nodes
  • General info on digital signature handling in APIs (varies by implementation)

Discussion