Overview
This node integrates with the TANSS API to manage devices such as PCs, servers, peripherals, hardware components, and software services. It supports creating, retrieving, listing, updating, and deleting device records in the TANSS system. This is useful for IT asset management workflows where automated synchronization or management of device inventories is required.
Practical examples:
- Automatically add new computers or peripherals to the TANSS inventory when they are provisioned.
- Retrieve detailed information about a specific device for reporting or auditing.
- Update device details like location or IP address after physical moves or network changes.
- Remove decommissioned devices from the inventory to keep records up to date.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: PC/Server, Peripherie (peripherals), Komponenten (components), Services (software services) |
| API Token | API token from TANSS authentication used for authorization |
| Gerätefelder | Collection of device fields used when creating or updating a device. Includes: |
| - Name: Device name | |
| - Beschreibung: Description of the device | |
| - 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 JSON data representing the response from the TANSS API for the requested operation. The structure depends on the operation:
- createDevice: JSON object with the newly created device's details.
- getDevice: JSON object with the requested device's details.
- listDevices: JSON array of device objects.
- updateDevice: JSON object with the updated device's details.
- deleteDevice: JSON object confirming deletion status.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL configured in credentials.
- Requires an API token from TANSS authentication provided as input.
- Uses HTTP requests with JSON payloads to communicate with the TANSS backend API.
Troubleshooting
- Missing Credentials: If no API credentials are found, the node throws an error "Keine Anmeldedaten gefunden!" Ensure that the API credential is properly configured in n8n.
- Empty Fields on Create/Update: Creating or updating a device without specifying any device fields results in an error. Always provide at least one field in the "Gerätefelder" collection.
- Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls return messages like "Fehler beim Ausführen von [operation]: [error message]". Check the API token validity, network connectivity, and correct device IDs.
Links and References
- TANSS API documentation (not 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/