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 creating, retrieving, listing, updating, and deleting device records in the TANSS system.
Typical use cases include:
- Automating inventory management by adding new devices or updating existing ones.
- Fetching detailed information about specific devices 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 update the location and status of peripherals after maintenance.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: PC/Server, Peripherie (peripherals), Komponenten (components), Services (software services). |
| API Token | API token obtained from TANSS authentication, required for authorization. |
Note: The following properties are conditional based on the selected operation:
| Name | Meaning |
|---|---|
| Operation | Action to perform: createDevice, getDevice, listDevices, updateDevice, deleteDevice. |
| Geräte-ID | Numeric ID of the device; required for getDevice, updateDevice, and deleteDevice operations. |
| Gerätefelder | Collection of device fields used when creating or updating a device. Includes: Name, Beschreibung (description), Seriennummer (serial number), Inventarnummer (inventory number), Hersteller-ID (manufacturer ID), Unternehmen-ID (company ID), Standort (location), IP-Adresse (IP address), MAC-Adresse (MAC address), Betriebssystem-ID (operating system ID). |
Output
The node outputs an array of JSON objects corresponding to the results of each input item processed. Each output JSON object contains the response data returned by the TANSS API for the requested operation.
- For createDevice, updateDevice, and getDevice, the output includes the details of the affected device.
- For listDevices, the output is a list of devices matching the specified device type.
- For deleteDevice, the output typically confirms successful deletion or returns relevant status information.
The node does not output binary data.
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 from TANSS authentication as an input property.
- Network connectivity to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If no credentials are found, the node throws an error "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 to set.
- Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is unrecognized.
- API Request Failures: Errors during API calls return messages prefixed with "Fehler beim Ausführen von [operation]:". Check the API token validity, network connection, and the correctness of device IDs.
- 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 in source; consult your TANSS provider)
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/