TANSS Geräte icon

TANSS Geräte

Verwaltet Geräte (PCs, Server, Peripherie) in der TANSS API
Join our community

Actions5

Overview

The "TANSS Geräte" node manages devices such as PCs, servers, peripherals, hardware components, and software services through the TANSS API. It supports operations to create, retrieve, list, update, and delete devices within the TANSS system.

This node is useful in IT asset management workflows where automated synchronization or management of device inventories is required. For example, it can be used to automatically list all registered servers, update device details after maintenance, or add new peripherals to the inventory.

For the selected operation "Geräte auflisten" (List Devices), the node fetches and returns a list of all devices of a specified type from the TANSS API.

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 API token obtained from TANSS authentication, used for authorizing API requests.

Output

The output is an array of JSON objects representing the devices retrieved from the TANSS API. Each object corresponds to a device with its properties as returned by the API.

Since this operation only lists devices, no binary data output is produced.

Example output structure (simplified):

[
  {
    "id": 123,
    "name": "Device Name",
    "description": "Description of the device",
    "serialNumber": "SN123456",
    "inventoryNumber": "INV7890",
    "manufacturerId": 45,
    "companyId": 12,
    "location": "Office 1",
    "ipAddress": "192.168.1.10",
    "macAddress": "00:11:22:33:44:55",
    "operatingSystemId": 3,
    ...
  },
  ...
]

Dependencies

  • Requires access to the TANSS API endpoint.
  • Needs an API token credential from TANSS authentication.
  • The base URL for the API is configured in the node credentials.
  • The node uses HTTP requests with JSON payloads.

Troubleshooting

  • No credentials found error: Ensure that the API token credential is properly set up and linked to the node.
  • Empty fields error on creation or update: When creating or updating devices, at least one device field must be provided; otherwise, the node throws an error.
  • Unrecognized operation error: This occurs if an unsupported operation value is passed; verify the operation parameter.
  • API request errors: Network issues, invalid tokens, or incorrect device IDs may cause request failures. Check the API token validity, device ID correctness, and network connectivity.
  • Permission issues: Make sure the API token has sufficient permissions for the requested operation.

Links and References

Discussion