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 servers to the TANSS inventory when they are provisioned.
- Update device details like location or IP address based on network scans or other data sources.
- Retrieve device information for reporting or auditing purposes.
- Remove decommissioned devices from the inventory.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: PC/Server, Peripherie (peripherals like printers), Komponenten (hardware components), Services (software services). |
| API Token | API token from TANSS authentication used to authorize requests. |
| Gerätefelder | Collection of device fields used when creating or updating a device. Includes: |
| - Name | Name of the device. |
| - Beschreibung | Description of the device. |
| - Seriennummer | Serial number of the device. |
| - Inventarnummer | Inventory number. |
| - Hersteller-ID | Manufacturer ID (number). |
| - Unternehmen-ID | Company ID associated with the device (number). |
| - Standort | Location of the device. |
| - IP-Adresse | IP address of the device. |
| - MAC-Adresse | MAC address of the device. |
| - Betriebssystem-ID | Operating system ID (number). |
Output
The node outputs JSON data representing the response from the TANSS API for each executed 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 "Keine Anmeldedaten gefunden!" Ensure that valid TANSS API credentials are configured in n8n.
- Empty Device Fields: When creating or updating a device, if no device fields are provided, the node throws errors indicating missing fields. Always provide at least one field for these operations.
- Invalid Operation: If an unsupported operation is selected, the node throws an error specifying the unknown operation.
- API Request Failures: Errors during API calls include the operation name and the original error message. Check network connectivity, API token validity, and endpoint correctness.
- Device ID Required: For operations like get, update, or delete, a valid device ID must be provided; otherwise, the request will fail.
Links and References
- TANSS API documentation (not publicly linked here) — consult your TANSS API provider for detailed API specs.
- n8n HTTP Request node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/