Overview
This node integrates with the TANSS API to manage PC or server records. It supports operations to create, retrieve, update, and delete PCs within the TANSS system. This is useful for IT administrators or service technicians who want to automate asset management tasks such as adding new machines, updating existing ones, fetching details, or removing obsolete entries.
Practical examples:
- Automatically creating a new PC record when onboarding a new employee.
- Fetching detailed information about a specific PC by its ID for inventory audits.
- Updating hardware or software details of a PC after maintenance.
- Deleting PC records that are no longer in use to keep the database clean.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token used to authenticate requests to the TANSS API. |
| PC ID | The unique identifier of the PC or server to fetch, update, or delete. |
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. This includes:
- For Get PC by ID: JSON object with the PC's details.
- For Create PC: JSON object with the newly created PC's data.
- For Update PC: JSON object with the updated PC's data.
- For Delete PC: JSON confirmation or status of deletion.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TANSS API.
- Needs an API token credential for authentication.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- The node uses HTTP methods (GET, POST, PUT, DELETE) to interact with the API endpoints.
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 updating/creating the PC.
When performing update or create operations, the node expects non-empty data fields. Provide at least one field in the PC Data collection.Failed to execute [operation]: [error message]
Indicates an error occurred during the API request. Common causes include invalid PC ID, expired API token, network issues, or insufficient permissions. Verify the API token validity, PC ID correctness, and network connectivity.The operation "[operation]" is not recognized.
This error should not occur under normal usage since operations are predefined. If it does, check that the operation parameter is correctly set.
Links and References
- TANSS API Documentation (not provided here; refer to your internal or vendor documentation)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/