Actions9
Overview
The "TANSS Support" node manages support entries and appointments via the TANSS API. It allows 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 need to track and manage technical support services, appointments, and related administrative data efficiently. For example, a service company can use this node to log support sessions performed by technicians, filter support records by customer or type, analyze support efforts over time, or attach digital signatures to support entries.
Practical examples:
- Creating a new support entry after completing a service call.
- Searching support records by customer name to review past interactions.
- Listing all support entries within a specific date range and location.
- Updating an existing support record with additional details.
- Uploading a signature image to confirm service completion.
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: Type of planning (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). - Beschreibung: Description text for the support entry. - Nicht berechnete Dauer (Minuten): Duration not charged. - Kostenstellen-ID: Cost center ID. - Support-Typ-ID: Support type ID. - Link-Typ-ID: Link type for assignment. - Link-ID: ID of the assignment link. |
Output
The node outputs JSON objects representing the response from the TANSS API for each executed operation. The structure depends on the operation but generally includes support entry data such as IDs, timestamps, descriptions, durations, types, and related metadata.
If binary data were involved (e.g., signature images), it would be handled accordingly, but this node only uploads signatures via JSON requests and does not output binary data.
Dependencies
- Requires access to the TANSS API endpoint with a valid base URL configured in credentials.
- Needs an API token credential for authentication.
- Uses HTTP methods (GET, POST, PUT) to interact with the TANSS backend API.
- No additional external libraries beyond n8n's standard workflow helpers.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token is correctly set.
- Required Fields Missing: For operations like creating or updating support, if required fields are empty, errors like "Keine Felder für die Support-Erstellung angegeben." (No fields specified for support creation) occur. Provide necessary support field values.
- Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is unrecognized.
- API Request Failures: Errors during HTTP requests return messages prefixed with "Fehler beim Ausführen von [Operation]:", indicating issues such as network problems, invalid tokens, or malformed requests. Verify API connectivity and input parameters.
- Date Format Issues: Dates must be provided in a format convertible to timestamps; otherwise, the API may reject them.
Links and References
- TANSS API Documentation (not provided here, but refer to your internal TANSS API docs)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/