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 devices within the TANSS system.
Typical use cases include:
- Automating device inventory management by creating or updating device records.
- Retrieving detailed information about specific devices for reporting or auditing.
- Cleaning up obsolete devices by deleting them from the system.
- Listing all devices of a certain type for synchronization or monitoring purposes.
For example, an IT administrator could use this node to automatically add new servers to the TANSS database when they are provisioned, or remove devices that have been decommissioned.
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 via TANSS authentication, required for authorization. |
| Geräte-ID | Numeric ID of the device to retrieve, update, or delete. Required for these operations. |
Output
The node outputs JSON data representing the response from the TANSS API for each executed operation. The structure depends on the operation:
- Create Device: Returns the created device object with its details.
- Get Device: Returns the device object identified by the given ID.
- List Devices: Returns an array of device objects of the specified type.
- Update Device: Returns the updated device object.
- Delete Device: Returns confirmation or status of the deletion.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TANSS API endpoint.
- Needs an API token credential from TANSS authentication to authorize requests.
- The base URL for the TANSS API is configured in the node credentials.
- Uses HTTP methods GET, POST, PUT, DELETE to interact with the API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error "Keine Anmeldedaten gefunden!" (No login data found!). Ensure the API token is correctly set.
- Empty Fields on Create/Update: Creating or updating a device without specifying any fields results in an error indicating no fields were provided. Always supply at least one field when creating or updating.
- Invalid Operation: Selecting an unsupported operation causes an error stating the operation is not recognized.
- API Request Failures: Errors during API calls return messages like "Fehler beim Ausführen von [operation]: [error message]". Check network connectivity, API token validity, and correct device IDs.
- Device ID Required: For get, update, and delete operations, a valid device ID must be provided; otherwise, the request will fail.
Links and References
- TANSS API Documentation (not provided here, but users should refer to their official API docs)
- n8n HTTP Request Node documentation for understanding request options and error handling
- General REST API best practices for managing device inventories