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 audits or reporting.
- Cleaning up obsolete devices by deleting them from the system.
- Listing all devices of a certain type for overview or synchronization purposes.
For example, an IT administrator could use this node to automatically add new servers to the TANSS database after provisioning, or remove decommissioned peripherals without manual intervention.
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 in API requests. |
| 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 assigned properties.
- Get Device: Returns the details of the specified device.
- List Devices: Returns an array of devices of the selected 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 must be configured in the node credentials.
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 for Create/Update: When creating or updating a device, if no fields are provided, the node throws errors indicating missing device fields. Always specify at least one field when performing these operations.
- Invalid Operation: If an unsupported operation is selected, the node will report it as unrecognized.
- 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, ensure a valid device ID is provided; otherwise, the API call will fail.
Links and References
- TANSS API Documentation (not included in source; consult your TANSS API provider)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage guidelines within n8n: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.http-request/