Actions9
Overview
This node integrates with the TANSS API to manage support entries and appointments. It allows users to retrieve filtered lists of support records, search supports by various criteria (ID, customer, content, type), create new support entries, update existing ones, analyze support data, and upload signatures for support entries.
A common use case is automating the retrieval and management of technical support schedules and records within an organization, enabling streamlined workflows for service technicians and support teams. For example, a user can fetch all support appointments within a specific timeframe and location or create a new support entry after completing a service call.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for authorization. |
| Filter-Optionen | Collection of filters to refine the list of support entries when retrieving them. Includes: - Zeitraum von / bis: Start and end date/time for filtering. - Support-Standorte: Locations like Büro (Office), Kunde (Customer), Remote. - Planungstypen: Types such as Support, Terminvorschlag (Appointment Proposal), Urlaub (Vacation), etc. - Unternehmen-IDs: Comma-separated company IDs. - Mitarbeiter-IDs: Comma-separated employee (technician) IDs. - Interner Support: Filter for internal/external/all support. - Textfilter: Text search in support descriptions. - Support-Typ-IDs: Comma-separated support type IDs. - Ticket-IDs: Comma-separated ticket IDs. - Offene Tickets: Filter by ticket status (all, only open, only closed, all except open). |
| Support-ID | Numeric ID of a support entry, used for operations that require specifying a particular support record. |
| Kundenname/Unternehmen | Customer or company name used for searching support entries by customer. |
| Suchtext | Text string used to search within support descriptions. |
| Support-Typ-ID | Numeric ID of a support type, used for searching support entries by type. |
| Analyse-Optionen | Options for analyzing support entries, including: - Zeitraum von / bis: Date range for analysis. - Gruppierung: Grouping method (by type, employee, company, or month). |
| Support-Felder | Fields for creating or updating a support entry, including: - Ticket-ID - Datum (date/time) - Dauer (duration in minutes) - Standort (location: Büro, Kunde, Remote) - Planungstyp (planning type) - Mitarbeiter-ID (employee ID) - Auftraggeber-ID (remitter ID) - Beschreibung (description text) - Nicht berechnete Dauer (non-billable duration) - Kostenstellen-ID (cost center ID) - Support-Typ-ID - Link-Typ-ID - Link-ID |
Output
The node outputs an array of JSON objects corresponding to the results returned by the TANSS API for the selected operation. The structure depends on the operation but generally includes detailed support entry data such as IDs, dates, durations, locations, descriptions, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication.
- The base URL for the TANSS API must be configured in the node credentials.
- Network connectivity to the TANSS backend API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token is correctly set.
- Required Parameters Missing: Some operations require mandatory parameters (e.g., customer name for searching by customer, support type ID for searching by type). Omitting these will cause errors indicating the missing parameter.
- Invalid IDs or Filters: Providing malformed or non-numeric IDs in comma-separated lists may result in empty or failed queries. Validate input formats.
- API Errors: Any HTTP or API errors during requests will be caught and reported with messages like "Fehler beim Ausführen von [Operation]: [Error message]". Check API token validity, network issues, and API availability.
- Empty Field Sets: Creating or updating support entries without any fields specified will raise errors prompting to provide necessary data.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n Documentation: Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node