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. The structure depends on the operation:
- Get PC by ID: Returns the details of the specified PC as a JSON object.
- Create PC: Returns the newly created PC's data.
- Update PC: Returns the updated PC data.
- Delete PC: 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 for authentication.
- The base URL for the TANSS API is obtained from the configured credentials.
- Proper network access to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If the API token or credentials are not provided or invalid, the node will throw an error "No credentials returned!" Ensure the API token is correctly set.
- Empty Data for Create/Update: When creating or updating a PC, if no data fields are provided, the node throws an error indicating missing data. Always provide at least one field in the PC Data collection.
- Invalid Operation: If an unsupported operation is selected, the node will report it as unrecognized.
- API Request Failures: Network issues, invalid tokens, or incorrect PC IDs can cause request failures. The node surfaces these errors with messages like "Failed to execute [operation]: [error message]". Verify API token validity, PC ID correctness, and network connectivity.
Links and References
- TANSS API Documentation (refer to your internal or vendor-provided API docs)
- n8n Documentation on HTTP Request Node and Custom Nodes (for general understanding)