Actions9
Overview
This node integrates with the TANSS API to manage support entries and appointments. It allows users to search, list, create, update, analyze, and upload signatures for support records related to customers or companies. This is useful in scenarios where a company needs to track and manage technical support services, appointments, and related data efficiently.
For example, a user can:
- Search support tickets by customer name to quickly find all relevant support cases.
- Create new support entries with detailed information such as date, duration, location, and type.
- Analyze support data over a specific time period grouped by type, employee, or company.
- Upload signatures to confirm support completion.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform. Options include: Support list retrieval, search by ID, customer, content, type; create, update, analyze support; upload signature. |
| API Token | API token from TANSS authentication used for authorization. |
| Support-ID | ID of the support entry (required for get, update, upload signature operations). |
| Kundenname/Unternehmen (Customer Name) | Customer or company name used to search support entries (for "searchByCustomer" operation). |
| Suchtext (Search Text) | Text to search within support descriptions (for "searchByContent" operation). |
| Support-Typ-ID | ID of the support type (for "searchByType" operation). |
| Analyse-Optionen (Analysis Options) | Collection of options for analysis including date range and grouping criteria (type, employee, company, month). |
| Filter-Optionen (Filter Options) | Collection of filters for listing supports, e.g., timeframe, locations, planning types, companies, employees, internal/external support, text filter, support types, tickets, ticket status. |
| Support-Felder (Support Fields) | Collection of fields for creating or updating support entries, including ticket ID, date, duration, location, planning type, employee ID, remitter ID, description, non-billed duration, cost center ID, support type ID, link type ID, link ID. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation performed but generally includes support entry details such as IDs, dates, descriptions, types, and related metadata.
If binary data were involved (e.g., uploading signatures), it would be handled accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authentication.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- No additional external libraries beyond n8n's standard helpers are required.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found).
- Required Parameters Missing: For operations like searching by customer or type, missing required parameters (e.g., customer name or support type ID) 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 may cause request failures, reported with messages like "Fehler beim Ausführen von [operation]: [error message]". Check API token validity and network connectivity.
- Empty Field Collections: Creating or updating support entries without specifying any fields results in an error prompting to provide necessary fields.
Links and References
- TANSS API documentation (not provided here, but users should refer to their official TANSS API docs for detailed endpoint info)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
If you need further details on other operations or properties, feel free to ask!