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 need to automate handling of support tickets, track service appointments, and analyze support data.
A practical example: You can use this node to fetch a specific support entry by its ID to review details, or to create new support appointments automatically from another system. It also supports searching support entries by customer name, content, or type, enabling flexible querying of support data.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for all operations. |
| Support-ID | Numeric ID of the support entry; used in operations that require specifying a support record (e.g., 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 connection to the TANSS API endpoint.
- Needs an API token credential from TANSS authentication configured in n8n credentials.
- The base URL for the TANSS API is taken from the stored credentials.
- The node uses HTTP requests with JSON payloads to communicate with the API.
Troubleshooting
- Missing Credentials Error: If no API token credential is found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure the API token credential is properly set up in n8n.
- Invalid Support-ID: Providing an invalid or non-existent Support-ID may cause the API to return an error or empty result.
- Operation Not Recognized: If an unsupported operation value is provided, the node will throw an error indicating the operation is not recognized.
- Required Parameters Missing: For some operations like searching by customer or creating/updating support, missing required parameters (e.g., customer name, support fields) will cause errors.
- API Request Failures: Network issues or incorrect API tokens can lead to request failures with messages like "Fehler beim Ausführen von getSupport: ...". Verify network connectivity and token validity.
Links and References
- TANSS API Documentation (not included here; refer to your TANSS API provider for official docs)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/