Actions40
- Computer Actions
- Monitor Actions
- Printer Actions
- Network Equipment Actions
- Phone Actions
- Software Actions
- Peripheral Actions
- Software License Actions
Overview
This node interacts with the Kennis Flux IT Service Management and Asset Tracking system, specifically allowing operations on various GLPI categories such as Assets, Assistance, Administration, Management, and Dropdowns. The 'Delete' operation for Network Equipment enables users to delete a specific record by its ID within a chosen category. This is useful for automating the removal of outdated or incorrect network equipment records in IT asset management workflows.
Use Case Examples
- Deleting a network equipment record by specifying its category and ID to keep the asset database up to date.
- Automating cleanup of helpdesk tickets or ITSM records related to network equipment by deleting resolved or obsolete entries.
Properties
| Name | Meaning |
|---|---|
| Category | The GLPI category to work with, such as Assets, Assistance, Administration, Management, or Dropdowns. |
| ID | The unique identifier of the record to delete within the selected category. |
| Options | Additional request options such as language for localized content, entity ID for the request, and whether to apply the entity recursively. |
Output
JSON
json- The JSON response from the GLPI API after attempting to delete the specified record. This may include success confirmation or error details.
Dependencies
- Requires an OAuth2 API credential for GLPI with client ID, client secret, username, and password to authenticate requests.
Troubleshooting
- Common issues include invalid or missing ID causing the delete operation to fail, resulting in error messages from the GLPI API.
- OAuth2 token request failures due to incorrect credentials or network issues will prevent the node from executing successfully.
- Invalid JSON in additional fields (if used in other operations) can cause errors, but for delete operation this is less relevant.
- To resolve errors, verify the ID exists, credentials are correct, and the GLPI API endpoint is reachable.
Links
- GLPI Official Documentation - Comprehensive resource for understanding GLPI API and its categories.
- OAuth 2.0 Authorization Framework - Details on OAuth2 authentication used by the node to connect to GLPI API.