Overview
This node integrates with the TANSS API to manage various types of devices such as PCs, servers, peripherals (e.g., printers, scanners), hardware components, and software services. It supports operations to create, retrieve, list, update, and delete device records within the TANSS system.
Typical use cases include:
- Automating inventory management by adding new devices or updating existing ones.
- Fetching detailed information about a specific device for reporting or auditing.
- Listing all devices of a certain type to synchronize with other systems.
- Removing obsolete or decommissioned devices from the inventory.
For example, an IT administrator could use this node to automatically add newly purchased servers into the TANSS database or to retrieve the details of a printer before scheduling maintenance.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: PC/Server, Peripherie (peripherals), Komponenten (components), Services (software services). |
| Operation | Action to perform on the device(s). Options: Gerät erstellen (create device), Gerät abrufen (get device), Geräte auflisten (list devices), Gerät aktualisieren (update device), Gerät löschen (delete device). |
| API Token | API token obtained from TANSS authentication, used for authorizing requests. |
| Geräte-ID | Numeric ID of the device; required for getDevice, updateDevice, and deleteDevice operations. |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation:
- For getDevice, it returns the detailed data of the specified device.
- For listDevices, it returns an array of devices matching the selected device type.
- For createDevice and updateDevice, it returns the created or updated device data.
- For deleteDevice, it returns confirmation of deletion or related status.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint, configured via credentials that provide the base URL and an API key/token.
- The user must supply a valid API token for each request, which is passed in the HTTP header.
- Network connectivity to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials Error: If no credentials are found, the node throws "Keine Anmeldedaten gefunden!" Ensure that the API credentials are properly configured in n8n.
- Empty Fields for Create/Update: When creating or updating a device, if no device fields are provided, the node throws errors like "Keine Felder für die Geräteerstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." Always specify at least one field when performing these operations.
- Invalid Operation: If an unsupported operation is selected, the node will throw an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls return messages prefixed with "Fehler beim Ausführen von [operation]:". Check the API token validity, device IDs, and network connectivity.
- Device ID Required: For operations that require a device ID (get, update, delete), ensure a valid numeric ID is provided.
Links and References
- TANSS API documentation (not included here; consult your TANSS API provider)
- n8n documentation on creating custom nodes and handling HTTP requests: https://docs.n8n.io/
- General REST API usage best practices