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:
- Automating inventory management by adding new devices or updating existing ones.
- Fetching detailed information about a specific device for reporting or auditing.
- Listing all devices of a certain type to synchronize with other systems.
- Removing obsolete or decommissioned devices from the database.
For example, you could use this node to automatically add newly purchased computers to your asset management system or to retrieve details about a printer before scheduling maintenance.
Properties
| Name | Meaning |
|---|---|
| Gerätetyp | Type of device to manage. Options: PC/Server, Peripherie (peripherals like printers), Komponenten (hardware components), Services (software services). |
| Operation | Action to perform on the device resource. Options: Gerät erstellen (create device), Gerät abrufen (get device), Geräte auflisten (list devices), Gerät aktualisieren (update device), Gerät löschen (delete device). |
| API Token | API token obtained via TANSS authentication, required for authorization. |
| Geräte-ID | Numeric ID of the device; required for get, update, and delete operations. |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. The structure depends on the operation:
- Create Device: Returns the created device object with its assigned properties.
- Get Device: Returns detailed information about the specified device.
- List Devices: Returns an array of device objects matching the selected device type.
- Update Device: Returns the updated device object reflecting changes.
- Delete Device: Returns confirmation of deletion or related status.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint, configured via credentials that provide the base URL and an API token.
- The user must supply a valid API token for each execution.
- 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 on Create/Update: Creating or updating a device without specifying any fields results in errors like "Keine Felder für die Geräteerstellung angegeben." or "Keine Felder zum Aktualisieren angegeben." Always provide at least one field when creating or updating.
- Invalid Operation: Selecting an unsupported operation triggers an error indicating the operation is not recognized.
- API Request Failures: Errors during API calls return messages prefixed with "Fehler beim Ausführen von [operation]:". Check network connectivity, API token validity, and correct device IDs.
- Device ID Required: For get, update, and delete operations, ensure a valid device ID is provided; otherwise, the request will fail.
Links and References
- TANSS API Documentation (not provided here; consult your internal resources)
- n8n Documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage best practices