Actions9
Overview
The "TANSS Support" node manages support entries and appointments via the TANSS API. It enables users to retrieve, create, update, search, analyze, and upload signatures related to support records. This node is particularly useful for organizations that track technical support activities, service appointments, or customer interactions within the TANSS system.
A common scenario includes analyzing support data over a specific period grouped by type, employee, company, or month to gain insights into support workload or performance. Another practical use case is creating new support entries automatically from incoming tickets or updating existing ones based on workflow triggers.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for all operations. |
| Analyse-Optionen | Options for analyzing support entries: |
| - Zeitraum von (dateFrom): Start date for analysis period | |
| - Zeitraum bis (dateTo): End date for analysis period | |
| - Gruppierung (groupBy): Grouping criteria for analysis; options are: | |
| - Nach Typ (type) | |
| - Nach Mitarbeiter (employee) | |
| - Nach Unternehmen (company) | |
| - Nach Monat (month) |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. The structure depends on the operation but generally includes support entry details such as IDs, dates (timestamps), descriptions, types, employees involved, companies, durations, and other metadata.
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 the user to configure credentials with the base URL of the TANSS API and provide the API token at runtime.
- No additional external libraries beyond n8n's standard HTTP request helper are used.
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 Parameters Missing: For some operations like searching by customer or type, missing required parameters (e.g., customer name or support type ID) will cause errors indicating the missing input.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Network issues or invalid tokens may cause request failures with messages like "Fehler beim Ausführen von [operation]: [error message]". Verify network connectivity and token validity.
- Date Format: Date inputs are converted to timestamps internally. Providing invalid date formats might cause unexpected results or errors.
Links and References
- TANSS API Documentation (not publicly provided here; consult your TANSS API provider)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/