AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node interacts with the AvantGuard NinjaOne API to retrieve information about installed operating system patches on devices. Specifically, the "Get Installed OS Patches" operation fetches a list of OS patches that have been installed, optionally filtered by various criteria such as device, patch status, installation date, and pagination controls.

This node is useful in IT management and security automation workflows where you need to monitor patch compliance, audit installed updates, or trigger further actions based on patch status. For example, it can be used to generate reports of failed patches, identify devices missing critical updates, or automate remediation steps.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination options for the query:
- Df Device filter — specify which device(s) to query patches for
- Status Patch status filter — possible values: FAILED, INSTALLED
- Installed Before Include patches installed before this date (date string)
- Installed After Include patches installed after this date (date string)
- Cursor Cursor name for pagination control
- Page Size Limit number of records returned per page (number)

These parameters allow fine-tuning the query to get exactly the subset of installed patches needed.

Output

The node outputs JSON data representing the list of installed OS patches matching the query parameters. Each item in the output typically includes details about the patch such as its identifier, installation status, installation date, and associated device information.

If the API supports pagination, the output may also include cursor or paging tokens to retrieve subsequent pages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Invalid query parameters: Check that date strings are properly formatted and that status values are one of the allowed options (FAILED, INSTALLED).
  • Pagination issues: If using cursors, verify that the cursor value is valid and corresponds to a previous response.
  • Empty results: May indicate no patches match the filters; try broadening or removing filters to confirm connectivity.
  • API rate limits or downtime: Handle HTTP errors gracefully and consider retry logic if supported.

Links and References

Discussion