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
Devices → Get Device Processors
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about device processors. Specifically, the "Get Device Processors" operation fetches details about the processors installed on a specified device by its identifier. This is useful in IT management scenarios where you need to audit hardware specifications, monitor device configurations, or integrate device inventory data into workflows.
Practical examples include:
- Automatically gathering processor details of devices for asset management.
- Triggering alerts or reports based on processor types or counts.
- Enriching device records in other systems with up-to-date hardware info.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the device whose processors you want to retrieve. |
Output
The node outputs JSON data representing the processor information of the specified device. The exact structure depends on the NinjaOne API response but typically includes details such as processor model, speed, core count, and other relevant hardware attributes.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the user to configure an API credential (OAuth2 token) for authenticating requests.
- 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 an existing device in NinjaOne.
- Authentication errors: Verify that the OAuth2 credentials are valid and have sufficient permissions to access device data.
- API request failures: Check network connectivity and NinjaOne service status if requests fail.
- No binary data errors: Not applicable here since this operation does not handle binary data.
Common error messages will relate to HTTP request failures or missing parameters; resolving them usually involves correcting input values or updating credentials.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and responses)
- n8n OAuth2 Credential Setup (for configuring OAuth2 authentication)