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. This is useful in scenarios where a company needs to track and manage technical support tickets, service appointments, or customer interactions systematically.
For example, a support team can use this node to:
- Search support entries by customer name to quickly find all relevant tickets.
- Retrieve detailed information about a specific support entry by its ID.
- Create new support records when a service call is scheduled.
- Analyze support data over a time period grouped by type or employee to generate reports.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform on support entries. Options include: |
| - Support-Liste abrufen (List supports) | |
| - Support nach ID suchen (Get support by ID) | |
| - Support nach Kunde suchen (Search support by customer name/company) | |
| - Support nach Inhalt suchen (Search support by content text) | |
| - Support nach Typ suchen (Search support by support type) | |
| - Support erstellen (Create a new support entry) | |
| - Support aktualisieren (Update an existing support entry) | |
| - Support analysieren (Analyze support entries) | |
| - Signatur hochladen (Upload signature for a support entry) | |
| API Token | API token from TANSS authentication required for accessing the API. |
| Support-ID | Numeric ID of the support entry (required for get, update, upload signature operations). |
| Kundenname/Unternehmen | Customer or company name used to search support entries (required for "searchByCustomer"). |
| Suchtext | Text string to search within support descriptions (for "searchByContent" operation). |
| Support-Typ-ID | Numeric ID of the support type (for "searchByType" operation). |
| Analyse-Optionen | Collection of options for analysis including date range and grouping criteria. |
| Filter-Optionen | Collection of filters for listing supports such as timeframe, locations, planning types, companies, employees, internal/external filter, text filter, support types, tickets, and ticket status. |
| Support-Felder | Collection of fields for creating or updating support entries, e.g., ticket ID, date, duration, location, planning type, employee ID, description, cost center ID, support type ID, etc. |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. The structure depends on the operation:
- For listing or searching supports, it returns arrays of support entries matching the criteria.
- For getting a support by ID, it returns detailed information about that single support entry.
- For creating or updating, it returns the created or updated support record.
- For analysis, it returns aggregated data based on the specified grouping.
- For uploading a signature, it returns confirmation or status of the upload.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential obtained via TANSS authentication.
- The base URL for the TANSS API must be configured in the credentials.
- Uses HTTP requests with JSON payloads to communicate with the API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node throws an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token is correctly set.
- Required Parameters Missing: For some operations like searching by customer or support type, missing required parameters (e.g., customer name or support type ID) will cause errors indicating the missing input.
- Invalid IDs: Providing invalid or zero IDs for support entries or types may result in API errors or empty results.
- API Errors: Network issues or incorrect API tokens can cause request failures. The node surfaces these with messages like "Fehler beim Ausführen von [operation]: [error message]".
- Empty Field Collections: Creating or updating support entries without specifying any fields will throw errors prompting to provide necessary data.
To resolve these issues:
- Verify all required inputs are provided.
- Check API token validity and permissions.
- Confirm IDs and filter values are correct and formatted properly.
- Review network connectivity to the TANSS API.
Links and References
- TANSS API documentation (not publicly provided here; consult your TANSS API provider)
- n8n HTTP Request node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/