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 customer service or technical support activities.
The specific operation "Support nach Typ suchen" (Search Support by Type) enables filtering support entries by a given support type ID. This is useful when you want to retrieve all support records associated with a particular category or type of service.
Practical examples:
- Retrieve all support tickets related to hardware issues by specifying the corresponding support type ID.
- Filter support entries to analyze workload distribution across different support types.
- Automate reporting on specific categories of support services.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
| Support-Typ-ID | The ID of the support type to filter support entries by. This must be provided for the "searchByType" operation. |
Output
The node outputs an array of JSON objects representing the support entries returned by the TANSS API based on the search criteria. Each item in the output corresponds to one support record with its full details as provided by the API.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authentication with the TANSS API.
- The base URL for the TANSS API is configured in the node credentials.
- Network connectivity to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating that no login data was found.
- Required Parameters Missing: For the "searchByType" operation, if the Support-Typ-ID is not provided or zero, the node throws an error stating that the Support-Typ-ID is required.
- API Request Failures: Errors during the HTTP request to the TANSS API will result in an error message including the operation name and the original error message. Check network connectivity, API token validity, and API endpoint availability.
- Invalid Operation: If an unsupported operation is selected, the node will throw an error indicating the operation is not recognized.
Links and References
- TANSS API Documentation (Replace with actual link if available)
- n8n Documentation on Creating Custom Nodes