Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
The node integrates with the AvantGuard NinjaOne system to retrieve detailed information about devices managed within that system. Specifically, the "Get Devices Detailed" operation fetches a list of devices along with their comprehensive details. This is useful for IT administrators or automation workflows that need to inventory devices, monitor device status, or perform audits.
Practical examples include:
- Automatically generating reports on all devices in an organization.
- Feeding device data into asset management or monitoring systems.
- Filtering devices based on specific criteria such as device type or pagination controls.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional parameters to refine the device query: - Df: Device filter (string) - Page Size: Limit number of devices returned (number) - After: Last Node ID from previous page for pagination (number) |
Output
The node outputs JSON data containing detailed information about devices retrieved from the NinjaOne system. The structure typically includes device attributes such as device identifiers, names, statuses, and other metadata provided by the API.
If binary data were supported, it would represent device-related files or attachments, but this node focuses on JSON device details only.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
- Needs the base URL of the NinjaOne API configured in the credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and the included OpenAPI specification (openapi.json) for request building and execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or unsupported query parameter values may result in empty responses or errors.
- Pagination parameters must be used carefully to avoid skipping or repeating devices.
Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- HTTP 400 errors may occur if query parameters are malformed.
- Network errors could indicate connectivity issues with the NinjaOne API endpoint.
To resolve these, verify API credentials, ensure query parameters conform to expected types and formats, and check network connectivity.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints and parameters)
- n8n Documentation for guidance on setting up credentials and using nodes with API integrations