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 'Peripheral - Get Many' operation retrieves multiple peripheral items from a selected GLPI category, such as IT assets, helpdesk tickets, user administration, management data, or dropdown reference data. It supports filtering, pagination, and localization options, making it useful for scenarios where bulk data retrieval or filtered queries of IT peripherals and related entities are needed, for example, fetching all active computers or helpdesk tickets within a certain category.
Use Case Examples
- Retrieve all IT assets like computers and printers for inventory management.
- Fetch a limited number of helpdesk tickets filtered by status for reporting.
- Get user and group administration data for synchronization with other systems.
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 query, including an RSQL filter string and a start index for pagination. |
| Options | Additional request options such as Accept-Language for localization, GLPI-Entity to specify the entity ID, and GLPI-Entity-Recursive to apply entity recursively. |
Output
JSON
json- The JSON response containing the retrieved peripheral items or entities from the GLPI API.
Dependencies
- Requires an OAuth2 API credential for GLPI with username, password, client ID, and client secret to authenticate and obtain an access token.
Troubleshooting
- Common issues include invalid JSON in additional fields, which causes a parsing error. Ensure JSON syntax is correct.
- OAuth2 token request failures due to incorrect credentials or network issues. Verify credentials and network connectivity.
- Operation not found errors if the specified category/resource/operation combination is invalid. Check the node parameters for correctness.
Links
- GLPI Project - Official site for GLPI ITSM and asset management system.