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 devices within the TANSS system.
Common scenarios include:
- Automatically syncing device inventories from TANSS into workflows.
- Creating new device records when provisioning hardware or software.
- Updating device details based on changes in asset management systems.
- Cleaning up obsolete device entries by deleting them via automation.
For example, you could use this node to list all PCs and servers registered in TANSS, then filter and process that data further in your workflow.
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 from TANSS authentication, required for authorization. |
| Geräte-ID | Numeric ID of the device, required for get, update, and delete operations. |
| Gerätefelder | Collection of fields describing device properties such as name, description, serial number, inventory number, manufacturer ID, company ID, location, IP address, MAC address, operating system ID. Used for create and update operations. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure depends on the operation:
- List Devices: An array of device objects matching the selected device type.
- Get Device: A single device object with detailed information.
- Create Device: The newly created device object returned by the API.
- Update Device: The updated device object after applying changes.
- Delete Device: Typically a confirmation or status message from the API.
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 to be provided as an input property.
- Uses HTTP requests to communicate with the TANSS backend API.
Troubleshooting
- Missing Credentials: If no credentials are found, the node throws "Keine Anmeldedaten gefunden!" Ensure the API credentials are properly set up in n8n.
- Empty Fields for Create/Update: When creating or updating a device, if no device fields are provided, the node throws an error indicating missing fields. Provide at least one field to proceed.
- Invalid Operation: If an unsupported operation is specified, the node will throw an error stating the operation is not recognized.
- API Request Failures: Errors during API calls return messages prefixed with "Fehler beim Ausführen von [operation]". Check the API token validity, network connectivity, and API endpoint correctness.
- Device ID Required: For get, update, and delete operations, a valid device ID must be supplied; otherwise, the request will fail.
Links and References
- TANSS API Documentation (not publicly linked here; refer to your internal TANSS API docs)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/