TANSS Support

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

Actions9

Overview

The "TANSS Support" node manages support entries and appointments via the TANSS API. It enables users to create, update, search, list, analyze, and upload signatures for support records related to service tickets and employee activities.

This node is beneficial in scenarios where organizations track technical support services, schedule appointments, or analyze support data for reporting. For example, a service company can automate creating support logs after completing a customer visit, search support entries by customer name or content, or generate reports grouped by support type or employee.

Specifically, the Support erstellen (Create Support) operation allows creating new support entries with detailed fields such as date, duration, location, employee, and description.

Properties

Name Meaning
API Token API token from TANSS authentication used to authorize requests.
Support-Felder Collection of fields describing the support entry to create or update:
• Ticket-ID: ID of the associated ticket.
• Datum: Start timestamp of the support.
• Dauer (Minuten): Duration in minutes.
• Standort: Location of support (Office, Customer, Remote).
• Planungstyp: Planning type (Support, Appointment Proposal, Fixed Appointment, Vacation, Illness, Absence, Standby, Private Appointment, Overtime).
• Mitarbeiter-ID: Employee ID performing the support.
• Auftraggeber-ID: ID of the remitter (employee who ordered the support).
• Beschreibung: Description text for the support entry.
• Nicht berechnete Dauer (Minuten): Duration not charged in minutes.
• Kostenstellen-ID: Cost center ID.
• Support-Typ-ID: Support type ID.
• Link-Typ-ID: Link type ID for assignment.
• Link-ID: ID of the linked entity.

Output

The node outputs JSON objects representing the response from the TANSS API for each executed operation. For the Support erstellen operation, the output JSON contains the newly created support entry details as returned by the API, including assigned IDs and stored field values.

No binary data output is produced by this node.

Dependencies

  • Requires an active TANSS API endpoint URL and a valid API token credential.
  • The node expects credentials configured in n8n containing the base URL of the TANSS API and the API token.
  • No additional external libraries beyond standard n8n workflow helpers are required.

Troubleshooting

  • Missing Credentials Error: If no API token or credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure that the API token credential is properly set up and selected.
  • Empty Support Fields: When creating or updating support entries, if no fields are provided, the node throws an error indicating missing fields. Always provide at least one support field.
  • Required Parameters Missing: For operations like searching by customer or type, missing required parameters (e.g., customer name or support type ID) cause errors. Provide all mandatory inputs.
  • API Request Failures: Errors during API calls include the operation name and the original error message. Check network connectivity, API token validity, and correct API endpoint configuration.
  • Date Format: Dates must be provided in a format parsable by JavaScript Date constructor; they are converted to timestamps internally.

Links and References

Discussion