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
This node interacts with the AvantGuard NinjaOne API to retrieve information about device processors. Specifically, the "Get Device Processors" operation fetches details about the processors installed in a specified device. This is useful for IT administrators or support teams who need to inventory hardware specifications or monitor device configurations within their managed environment.
Practical examples include:
- Gathering processor details for asset management.
- Verifying hardware compliance across devices.
- Automating reports on device performance capabilities.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device whose processor information you want to retrieve. This is a required numeric value. |
Output
The node outputs JSON data containing details about the processors of the specified device. The exact structure depends on the API response but typically includes fields such as processor model, speed, core count, and other relevant hardware attributes.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the device processors, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
- The base URL for the API must be configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building request properties and handling API interactions. - Uses an OpenAPI specification (
openapi.json) bundled with the node to define available operations and parameters.
Troubleshooting
- Missing or invalid device Id: Ensure that the "Id" property is set to a valid number corresponding to an existing device; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Confirm that the base URL is reachable and there are no firewall restrictions blocking access.
- Unexpected API responses: Check if the device exists and has processor information available; some devices might not return processor data if not properly inventoried.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- OpenAPI Specification