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 via its API. Specifically, the 'Monitor' resource with the 'Get Many' operation allows users to retrieve multiple records from various GLPI categories such as Assets, Assistance, Administration, Management, and Dropdowns. It supports filtering, pagination, and localization options, making it useful for scenarios like fetching lists of IT assets, helpdesk tickets, user profiles, or management documents for reporting or integration purposes.
Use Case Examples
- Retrieve all active computers from the Assets category for inventory management.
- Fetch a limited number of helpdesk tickets from the Assistance category with specific filters for status and priority.
- Get user profiles from the Administration category with localization in a specific language.
Properties
| Name | Meaning |
|---|---|
| Category | The GLPI category to work with, such as Assets, Assistance, Administration, Management, or Dropdowns. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return when 'Return All' is false. |
| Filters | Filters to apply on the results, including an RSQL filter string and a start index for pagination. |
| Options | Additional request options such as Accept-Language for localization, GLPI-Entity for entity ID, and GLPI-Entity-Recursive to apply entity recursively. |
Output
JSON
json- The retrieved data items from the GLPI API, each item representing a record from the selected category.
Dependencies
- Requires an OAuth2 API credential for authentication with the GLPI system, including client ID, client secret, username, and password.
Troubleshooting
- Common issues include invalid JSON in additional fields, which will cause an error indicating the JSON parsing problem.
- OAuth2 token request failures due to incorrect credentials or network issues will throw an error with details about the failure.
- Operation not found errors occur if the specified operation is not defined for the selected resource or category.
- To resolve errors, verify the correctness of input parameters, ensure valid OAuth2 credentials, and check network connectivity.