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 → Reboot Devices
AI-generatedOverview
This node integrates with the NinjaOne API to perform device management tasks. Specifically, the "Reboot Devices" operation under the "Management" resource allows users to remotely reboot a device identified by its ID. This is useful in IT automation scenarios where administrators need to restart devices for maintenance, updates, or troubleshooting without manual intervention.
Practical examples include:
- Automatically rebooting a workstation after deploying critical software updates.
- Forcing a reboot on a device that is unresponsive or stuck.
- Scheduling reboots as part of routine maintenance workflows.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device to reboot (number). |
| Mode | The reboot mode to use: either "NORMAL" for a standard reboot or "FORCED" for immediate forced reboot. |
| Reason | Optional text describing the reason for the reboot, which can be logged or audited. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting the reboot operation. This typically includes status information about the reboot request, such as success confirmation or error details.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the
ninjaOneOAuth2Apicredential configured in n8n to authenticate requests. - Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing device ID will cause the API call to fail.
- Insufficient permissions or expired OAuth2 token may result in authentication errors.
- Network connectivity problems can prevent the node from reaching the NinjaOne API.
Error messages and resolutions:
"No binary data exists on item!"or similar errors are not relevant here since this operation does not handle binary data.- API errors returned in the JSON response should be reviewed; they often indicate invalid parameters or permission issues.
- To resolve authentication errors, verify the OAuth2 credentials and refresh tokens if needed.
- Ensure the device ID corresponds to an existing device managed by NinjaOne.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and parameters)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials in n8n)