NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Devices → Get Device Installed Software Patches

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve information about software patches installed on a specific device. It allows filtering the patches by various criteria such as patch type, impact, status, product identifier, and installation date ranges. This is useful for IT administrators or support teams who want to audit or monitor the patch status of devices managed through NinjaOne.

Practical examples include:

  • Fetching all critical security patches installed on a device.
  • Listing patches installed before or after a certain date to verify compliance.
  • Filtering patches by product identifier to check updates for specific software.

Properties

Name Meaning
Id Device identifier (number) to specify which device's patches to retrieve (required).
Type Patch Type filter (string), e.g., security, feature, etc.
Impact Patch Impact filter (string), e.g., critical, moderate, low.
Status Patch Status filter (string), e.g., installed, pending, failed.
Product Identifier Product Identifier filter (string) to target patches related to a specific product.
Installed Before Include patches installed before this date (string, typically ISO date format).
Installed After Include patches installed after this date (string, typically ISO date format).

Output

The node outputs an array of JSON objects, each representing a software patch installed on the specified device that matches the applied filters. The exact structure depends on the NinjaOne API response but generally includes details such as patch name, type, impact, status, installation date, and associated product information.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node expects the NinjaOne OAuth2 API credentials to be configured in n8n.
  • Network access to the NinjaOne API endpoint is necessary.

Troubleshooting

  • Missing or invalid device ID: Ensure the "Id" property is set correctly and corresponds to a valid device in NinjaOne.
  • Authentication errors: Verify that the OAuth2 credentials are properly configured and have not expired.
  • Empty results: Check filter values; overly restrictive filters may return no patches.
  • Date format issues: Use ISO 8601 date strings for "Installed Before" and "Installed After" properties to avoid query errors.
  • API rate limits or downtime: If requests fail repeatedly, check NinjaOne service status and consider retry logic.

Links and References

Discussion