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. This is useful for IT service teams or customer support departments that track support tickets, appointments, and related activities in TANSS.
A practical example: You can use this node to fetch a specific support entry by its ID to review details or update it with new information after a service call. Another scenario is searching support entries by customer name or content to generate reports or follow up on open issues.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests |
| Support-ID | Numeric ID of the support entry (required for operations: getSupport, updateSupport, uploadSignature) |
Note on Operation "Support nach ID suchen" (getSupport)
- Requires API Token and Support-ID.
- Retrieves a single support entry by its unique ID.
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. For the "Support nach ID suchen" operation, the output JSON contains the detailed data of the requested support entry as returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network access to the TANSS backend API endpoint is necessary.
Troubleshooting
Error: "Keine Anmeldedaten gefunden!"
Means no API credentials were provided or found. Ensure you have configured the required API token credential correctly.Error: "Fehler beim Ausführen von getSupport: ..."
Indicates a failure during the API request. Check the API token validity, network connectivity, and that the Support-ID exists.Error: "Die Operation ... wird nicht erkannt."
Occurs if an unsupported operation value is set. Verify the operation parameter is one of the supported options.If the Support-ID is missing or zero for operations requiring it, the node may fail or return errors. Always provide a valid numeric Support-ID.
Links and References
- TANSS API documentation (not included here; refer to your TANSS provider)
- n8n documentation on creating custom nodes and using HTTP Request helpers