Actions9
Overview
This node integrates with the TANSS API to manage support entries and appointments. It allows users to retrieve, search, create, update, analyze, and upload signatures for support records within the TANSS system. Typical use cases include automating support ticket management, filtering support data by various criteria, scheduling or updating support appointments, and analyzing support activities over time.
Practical examples:
- Fetching a filtered list of support entries for reporting.
- Searching support tickets by customer name or content keywords.
- Creating new support appointments automatically from other workflows.
- Updating existing support records with new information.
- Uploading digital signatures related to support tasks.
- Analyzing support workload grouped by type, employee, company, or month.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each executed operation. The structure depends on the specific operation but generally includes support entry details such as IDs, dates (timestamps), descriptions, types, locations, employees involved, and other metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint, configured via credentials that provide the base URL and API authentication.
- The user must supply a valid API token for each execution.
- Network connectivity to the TANSS backend service is necessary.
Troubleshooting
- Missing Credentials: If no credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API credentials are properly configured in n8n.
- Required Parameters Missing: For some operations like searching by customer or creating/updating support, required parameters must be provided; otherwise, errors like "Kundenname ist erforderlich für die Suche." or "Keine Felder für die Support-Erstellung angegeben." will occur.
- Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during HTTP requests to the TANSS API will be reported with the message "Fehler beim Ausführen von [Operation]: [Error message]". Check network connectivity, API token validity, and request parameters.
- Date Formats: Date inputs are converted to timestamps internally. Invalid date formats may cause unexpected behavior.
Links and References
- TANSS API documentation (not provided here, but recommended to consult for detailed API usage)
- n8n documentation on creating custom nodes and using credentials
- General REST API best practices for troubleshooting HTTP request issues