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
Queries → Get Processors
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about processors (CPUs) from monitored devices. Specifically, the "Get Processors" operation under the "Queries" resource fetches processor data filtered by device, timestamp, pagination cursor, and page size.
Use cases include:
- Monitoring CPU details across devices in an IT environment.
- Fetching historical or current processor metrics for reporting or alerting.
- Paginating through large sets of processor records for analysis.
For example, you might use this node to get all processors active on a specific device at a given monitoring timestamp, limiting results to 50 per page.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: Specify a device identifier to filter processors belonging to that device. |
| Ts | Monitoring timestamp filter: Filter processors based on a specific monitoring timestamp. |
| Cursor | Cursor name: Used for paginating through results, indicating the position in the dataset. |
| Page Size | Limit number of records per page: Controls how many processor records are returned per request. |
Output
The node outputs JSON data representing the response from the NinjaOne API for the processors query. The structure typically includes an array of processor objects with their attributes (e.g., model, speed, cores), along with pagination metadata if applicable.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for NinjaOne to authenticate requests.
- Depends on the NinjaOne API being accessible and the user having appropriate permissions to query processor data.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect device filter or timestamp format may result in empty responses or errors.
- Pagination cursors must be used correctly; invalid cursors can cause errors or no data returned.
Error messages:
- Authentication errors indicate problems with the API key/token setup.
- Validation errors may occur if input parameters do not meet expected formats.
- Network or API downtime errors require checking NinjaOne service status.
To resolve these, verify credentials, ensure correct parameter formatting, and confirm NinjaOne API availability.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n documentation on OAuth2 Credentials