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 customers or companies. A typical use case is automating support ticket management workflows, such as retrieving support entries by customer name, filtering support lists by various criteria, or creating new support appointments programmatically.
For example, a user can search for all support entries related to a specific customer company, analyze support data over a time period grouped by type or employee, or update existing support records with new information.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests |
| Kundenname/Unternehmen (customerName) | Customer or company name to search support entries by (required for "Support nach Kunde suchen" operation) |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation but generally includes support entry details such as IDs, descriptions, dates, types, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authentication.
- The base URL for the TANSS API is provided via credentials configuration in n8n.
- Uses HTTP methods GET, POST, PUT depending on the operation.
Troubleshooting
- Missing Credentials: If no API token is provided or credentials are missing, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found). Ensure the API token is correctly configured.
- Required Parameters Missing: For operations like "Support nach Kunde suchen", if the customer name is empty, it throws an error indicating the required field is missing. Always provide mandatory fields.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Errors during HTTP requests return messages prefixed with "Fehler beim Ausführen von [operation]:". Check network connectivity, API token validity, and API endpoint availability.
- Date Fields: Date inputs are converted to timestamps; invalid date formats may cause errors.
Links and References
- TANSS API documentation (not provided here, but refer to your internal TANSS API docs)
- n8n HTTP Request node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/