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, planners, and administrators. 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, open only, closed only, all except open). |
Output
The node outputs JSON data representing the response from the TANSS API for the selected operation. For the "Support-Liste abrufen" operation, this will be a filtered list of support entries matching the specified criteria.
The output JSON structure depends on the API response but generally includes details about support records such as IDs, dates, durations, locations, types, employees involved, descriptions, and related tickets.
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.
- Uses HTTP requests with JSON payloads to communicate with the API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error indicating missing login data.
- Invalid or Missing Required Parameters: For operations like searching by customer or creating support entries, required parameters must be provided; otherwise, errors are thrown.
- API Request Failures: Network issues, invalid tokens, or server errors will cause request failures with error messages indicating which operation failed and why.
- Date Format Issues: Date/time inputs are converted to timestamps; incorrect formats may cause unexpected results.
- Empty Field Collections: Creating or updating support entries requires at least one field; empty input collections will trigger errors.
To resolve these:
- Ensure valid API token and credentials are set.
- Provide all required parameters for the chosen operation.
- Verify date/time inputs are correctly formatted.
- Check network connectivity and API availability.
Links and References
- TANSS API Documentation (not publicly linked here, refer to your organization's API docs)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n node development guide: https://docs.n8n.io/integrations/creating-nodes/