Overview
This node integrates with the TANSS API to manage PC or server records. It supports creating, updating, retrieving by ID, and deleting PCs or servers within the TANSS system. This is useful for IT asset management workflows where automated synchronization or manipulation of PC inventory data is required.
Typical use cases include:
- Automatically adding new PC records when provisioning hardware.
- Updating existing PC details such as location, software, or hardware specs.
- Fetching detailed information about a specific PC by its ID.
- Removing PC entries when decommissioned.
For example, you could automate the creation of a new PC record after a purchase order is approved, or update the PC's assigned employee after a transfer.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token used to authenticate requests to the TANSS API. |
| PC Data | A collection of fields describing the PC/server to create or update. Fields include: Inventory Number, Active status, Company ID, Name, Service Technician ID, Employee ID, Date (timestamp), Location, Manufacturer ID, Model, Serial Number, OS ID, Software, Remark, Show Remark (boolean), Mainboard Manufacturer ID, Mainboard Manufacturer Revision, Mainboard Serial Number, BIOS, BIOS Release, CPU Manufacturer ID, CPU Type ID, CPU Frequency, CPU Number, Mouse Serial Number, Keyboard Serial Number, Server (boolean), Internal Remark, Billing Number, Article Number, Manufacturer Number, Host ID, Purchase Price, Selling Price, Ownage Type (Own, Foreign, Own Rent, Foreign Rent), Storage ID, TeamViewer ID, TeamViewer Password, AnyDesk ID, AnyDesk Password, Reserved RAM, Reserved Hard Disk, Reserved CPU, Description. |
| Operation | The action to perform on the PC resource. Options are: "Get PC by ID", "Update PC", "Create PC", "Delete PC". |
| PC ID | The identifier of the PC or server to fetch, update, or delete. Required for all operations except "Create PC". |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. The structure of the JSON depends on the operation:
- For Create PC and Update PC, the output JSON contains the newly created or updated PC object returned by the API.
- For Get PC by ID, the output JSON contains the PC object fetched from the API.
- For Delete PC, the output JSON typically contains confirmation of deletion or an empty object.
No binary data is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication.
- The base URL for the TANSS API is obtained from the configured credentials.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
No credentials returned!
Occurs if the API token credential is missing or not configured properly. Ensure the API token is set in the node credentials.No data provided for creating/updating the PC.
When performing create or update operations, the PC Data collection must contain at least one field. Provide valid PC data to avoid this error.Failed to execute [operation]: [error message]
Indicates an HTTP request failure. Check the API token validity, network connectivity, and that the PC ID exists for get/update/delete operations.The operation "[operation]" is not recognized.
This should not occur unless the operation parameter is manually tampered with. Use only supported operations.
Links and References
- TANSS API documentation (not provided here; refer to your internal TANSS API docs)
- n8n HTTP Request helper documentation: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/