Actions9
Overview
The "TANSS Support" node manages support entries and appointments via the TANSS API. It enables users to retrieve, create, update, search, analyze, and upload signatures for support records. This node is useful in scenarios where companies want to automate or integrate their support ticketing and scheduling workflows with the TANSS system.
For example, a user can:
- Fetch filtered lists of support tickets within a specific timeframe.
- Search support entries by customer name, content, or type.
- Create new support entries or update existing ones.
- Analyze support data grouped by type, employee, company, or month.
- Upload digital signatures related to support entries.
This node streamlines support management processes by connecting n8n workflows directly to the TANSS backend.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used for authorization. |
| Analyse-Optionen | Collection of options for support analysis: |
| - Zeitraum von (Start date for analysis) | |
| - Zeitraum bis (End date for analysis) | |
| - Gruppierung (Grouping for analysis): Nach Typ, Nach Mitarbeiter, Nach Unternehmen, Nach Monat |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. The structure depends on the operation but generally includes support entry details, lists, or analysis results.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential for authentication.
- The node expects the TANSS API base URL to be configured in the credentials.
- No additional external dependencies are required beyond the TANSS API access.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error indicating missing login data.
- Required Parameters Missing: For operations like searching by customer or type, if mandatory parameters (e.g., customer name or support type ID) are not set, the node will throw errors specifying the missing input.
- Invalid Operation: If an unsupported operation is selected, the node will report that the operation is not recognized.
- API Request Failures: Network issues or invalid tokens may cause request failures; the node reports the error message returned by the API.
To resolve these issues:
- Ensure the API token is correctly entered and valid.
- Provide all required parameters for the chosen operation.
- Verify network connectivity and API endpoint availability.
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