Actions9
Overview
This node integrates with the TANSS API to manage support entries and appointments. It allows users to create, update, search, list, analyze, and upload signatures for support records related to service tickets and employee activities.
Typical use cases include:
- Automatically creating new support entries when a service is performed.
- Searching and filtering support records by customer, content, or type.
- Listing supports within specific timeframes or filtered by various criteria.
- Analyzing support data grouped by type, employee, company, or month.
- Uploading digital signatures associated with support entries.
For example, a service company could use this node to log support times, locations, and types for technicians, then analyze the data monthly to optimize resource allocation.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication required for all operations. |
| Support-Felder | Collection of fields used when creating or updating a support entry: - Ticket-ID: ID of the related 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 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 assignment link. |
Output
The node outputs an array of JSON objects corresponding to the response from the TANSS API for each executed operation. The structure depends on the operation but generally includes support entry details such as IDs, timestamps, descriptions, durations, employee info, and related ticket data.
No binary data output is produced by this node.
Dependencies
- Requires an API token credential for authenticating requests to the TANSS API.
- The base URL for the TANSS API is obtained from the configured credentials.
- The node uses HTTP methods (GET, POST, PUT) to interact with the API endpoints.
Troubleshooting
- Missing Credentials: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API token is correctly configured.
- Required Fields Missing: For creation or update operations, if no support fields are provided, errors like "Keine Felder für die Support-Erstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." occur. Provide necessary fields in the input.
- Invalid Parameters: Searches require specific parameters (e.g., customer name, search text, support type ID). Omitting these results in errors prompting to provide them.
- Unknown Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Network issues or invalid tokens cause request errors with messages including the operation name. Verify network connectivity and token validity.
Links and References
- TANSS API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node