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 users to update peripheral records within the system. It supports updating various fields of a peripheral, such as its name, comment, and additional custom fields, by sending authenticated API requests to the Kennis Flux backend. This node is useful for IT administrators and service desk personnel who need to programmatically manage and update peripheral assets in their IT environment, ensuring data consistency and automation in asset management workflows.
Use Case Examples
- Updating the name and comment of a peripheral device by specifying its ID and new field values.
- Adding custom JSON fields to a peripheral record to capture additional metadata not covered by default fields.
- Setting request options like language and entity context to tailor the update operation to specific organizational units or localization needs.
Properties
| Name | Meaning |
|---|---|
| Category | The GLPI category to work with, such as assets, assistance, administration, management, or dropdowns. |
| ID | The unique identifier of the peripheral record to update. |
| Fields | The fields to update on the peripheral, including name, comment, and additional JSON fields for custom data. |
| Options | Additional request options such as Accept-Language for localization, GLPI-Entity to specify the entity context, and GLPI-Entity-Recursive to apply entity settings recursively. |
Output
JSON
json- The updated peripheral record data returned from the Kennis Flux API.
Dependencies
- An OAuth2 API credential for authenticating requests to the Kennis Flux API, including client ID, client secret, username, and password.
Troubleshooting
- Invalid JSON in Additional Fields: Ensure that the JSON string provided in the Additional Fields property is correctly formatted to avoid parsing errors.
- OAuth2 token request failed: Check that the OAuth2 credentials (client ID, client secret, username, password) are correct and that the Kennis Flux API URL is reachable.
- Operation not found error: Verify that the specified category, resource, and operation are valid and supported by the node.
- HTTP request errors: Network issues or incorrect API endpoint paths can cause failures; verify connectivity and API paths.