Overview
This node integrates with the TANSS API to manage various types of devices such as PCs, servers, peripherals, 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:
- Automatically syncing device inventories from TANSS into workflows.
- Creating new device entries when provisioning hardware or software.
- Updating device details based on changes in asset management systems.
- Removing obsolete devices from the TANSS database.
For example, you could use this node to fetch detailed information about a specific PC by its ID or list all peripheral devices registered in TANSS.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: "PC/Server" (computers and servers), "Peripherie" (peripherals like printers, scanners), "Komponenten" (hardware components), "Services" (software services). |
| API Token | The API token obtained from TANSS authentication, required for authorization. |
| Geräte-ID | The unique identifier of the device, required for operations that target a specific device (get, update, delete). |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. This includes:
- For Gerät abrufen (getDevice): JSON object with detailed device information.
- For Geräte auflisten (listDevices): Array of device objects matching the selected device type.
- For Gerät erstellen (createDevice) and Gerät aktualisieren (updateDevice): JSON object reflecting the created or updated device.
- For Gerät löschen (deleteDevice): Typically a confirmation message or status.
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 depending on the operation.
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: When creating or updating a device, if no fields are specified, the node throws errors indicating missing data. Always provide at least one field to modify.
- Invalid Operation: If an unsupported operation is selected, the node reports it as unrecognized.
- API Request Failures: Errors during HTTP requests return messages prefixed with "Fehler beim Ausführen von [operation]". Check network connectivity, API token validity, and correct device IDs.
- Device ID Required: Operations like get, update, and delete require a valid device ID; omitting or setting it to zero may cause failures.
Links and References
- TANSS API Documentation (not provided here, but users should consult 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