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
Management → Reset Policy Overrides
AI-generatedOverview
This node interacts with the NinjaOne API to manage device policies, specifically allowing users to reset policy overrides on devices. It is useful in IT management scenarios where administrators need to revert any custom policy changes applied to a device back to default settings. For example, if a device has temporary policy modifications that should be cleared, this operation resets those overrides efficiently.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which the policy overrides will be reset. This is a required numeric value. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to reset the policy overrides on the specified device. The structure typically contains confirmation or status information about the reset operation. No binary data output is involved.
Dependencies
- Requires an active connection to the NinjaOne API.
- Needs an API authentication token configured via OAuth2 credentials within n8n.
- The node uses the NinjaOne API endpoints and expects proper permissions to perform management operations on devices.
Troubleshooting
Common issues:
- Invalid or missing device ID: Ensure the "Id" property is correctly set to a valid device identifier.
- Authentication errors: Verify that the OAuth2 credentials are correctly configured and have sufficient permissions.
- Network or API downtime: Check connectivity and NinjaOne service status.
Error messages:
"No binary data exists on item!"or similar errors related to binary data do not apply here since this operation does not handle binary inputs.- API error responses will be returned in the JSON output under an
errorfield if the node is set to continue on failure.
Resolving these usually involves verifying input parameters, credentials, and network conditions.
Links and References
- NinjaOne API Documentation (for detailed API endpoint info)
- n8n OAuth2 Credential Setup