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 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, content, or type.
- 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 of assignment. - Link-ID: ID of the assignment link. |
Output
The node outputs JSON data representing the response from the TANSS API for each executed operation. The structure depends on the operation performed but generally includes support entry details, lists of supports, analysis results, or confirmation of updates/signature uploads.
No binary data output is produced by this node.
Dependencies
- Requires an API token credential for authenticating with the TANSS API.
- Needs network access to the configured TANSS API base URL.
- The node expects the TANSS API to be available and responsive.
Troubleshooting
- Missing Credentials: If no API token is provided, the node throws an error "Keine Anmeldedaten gefunden!" (No credentials found). Ensure the API token is set correctly.
- Required Parameters Missing: Operations like searching by customer or content require specific parameters (e.g., customer name, search text). Omitting these will cause errors indicating the missing input.
- Empty Fields for Create/Update: Creating or updating support entries without specifying any fields will result in an error stating no fields were provided.
- Invalid Operation: Selecting an unsupported operation triggers an error mentioning the operation is not recognized.
- API Request Failures: Network issues or invalid tokens may cause request failures with error messages including the operation name and the underlying error message. Verify API token validity and network connectivity.
Links and References
- TANSS API Documentation (Assumed, please replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage guidelines within n8n workflows