Actions9
Overview
The "TANSS Support" node manages support entries and appointments via the TANSS API. It allows users to create, update, retrieve, 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 automate or integrate their support scheduling, tracking, and reporting processes with the TANSS system. For example:
- Automatically creating support entries after a service call.
- Updating existing support records with new details.
- Searching support logs by customer name or content keywords.
- Analyzing support data grouped by type, employee, company, or month.
- Uploading digital signatures for completed support tasks.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Support-ID | ID of the support entry to retrieve, update, or upload a signature for. |
| Support-Felder | Collection of fields for creating or updating a support entry: - Ticket-ID: ID of the associated ticket - Datum: Start date/time of the support (timestamp) - 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 in minutes - Kostenstellen-ID: Cost center ID - Support-Typ-ID: Support type ID - Link-Typ-ID: Link type ID for assignment - Link-ID: Link ID for assignment |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each executed operation. The structure depends on the operation performed but generally includes support entry data such as IDs, timestamps, descriptions, durations, employee info, and other metadata.
If binary data were involved (e.g., signature files), it would be indicated, but this node only uploads signatures and does not output binary data.
Dependencies
- Requires connection to the TANSS API endpoint.
- Needs an API token credential for authentication.
- The base URL for the TANSS API must be configured in the credentials.
- Uses HTTP methods GET, POST, PUT depending on the operation.
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 credential is set up correctly.
- Required Parameters Missing: Operations like searching by customer or updating support require specific parameters (e.g., customer name, support ID, or support fields). Omitting these will cause errors indicating the missing field.
- 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 can cause request failures with messages like "Fehler beim Ausführen von [operation]: [error message]". Verify network connectivity and token validity.
- Date Format: Dates must be provided in a format convertible to timestamps; otherwise, the API may reject the request.
Links and References
- TANSS API Documentation (not provided here, but users should refer to official TANSS API docs for detailed endpoint info)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage in n8n: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/