Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
System → Search
AI-generatedOverview
This node integrates with the NinjaOne API to perform various operations on different resources. Specifically, for the System resource with the Search operation, it allows users to search for devices or system entities based on a query string. This can include searching by device name, logged-on user name, IP address, or other identifying information.
Common scenarios where this node is beneficial include:
- Quickly locating specific devices in an IT environment by partial or full identifiers.
- Filtering devices to manage or audit them based on search criteria.
- Automating workflows that require device lookup before performing further actions.
For example, an IT administrator could use this node to find all devices currently logged in by a particular user or to locate devices within a certain IP range.
Properties
| Name | Meaning |
|---|---|
| Q | Search query string such as device name, logged-on user name, IP address, etc. |
| Limit | Maximum number of devices to return. Set to 0 for no limit (returns all matching items). |
Output
The node outputs an array of JSON objects representing the devices or system entities matching the search query. Each item in the output contains detailed information about a device as returned by the NinjaOne API's search endpoint.
The json field includes all relevant device data retrieved from the API.
This node does not output binary data.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
- The node uses HTTP GET requests to the NinjaOne API endpoints.
- No additional external dependencies beyond the NinjaOne API and n8n's built-in HTTP request helpers.
Troubleshooting
- Empty results: If the search returns no devices, verify that the query string (
Q) is correctly specified and matches existing devices. - API authentication errors: Ensure the API key or OAuth2 credentials are valid and have sufficient permissions.
- Limit parameter issues: Setting
Limitto 0 means no limit; if too many results are returned, consider setting a reasonable limit to avoid performance issues. - Missing or malformed input: Make sure the
Qproperty is provided as a non-empty string when performing a search. - Network or API errors: Check network connectivity and NinjaOne API status if requests fail unexpectedly.
Links and References
- NinjaOne API Documentation — Official API docs for reference on available endpoints and parameters.
- n8n HTTP Request Node — For understanding how HTTP requests are made within n8n nodes.