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 integrates with the AvantGuard NinjaOne API to manage devices, specifically allowing users to reboot devices remotely. The "Reboot Devices" operation lets you trigger a reboot on a specified device by its identifier, choosing between a normal or forced reboot mode. This is useful in IT management scenarios where remote maintenance or troubleshooting requires restarting machines without physical access.
Practical examples include:
- Remotely rebooting a workstation after deploying updates.
- Forcing a reboot on an unresponsive device to restore functionality.
- Scheduling reboots with reasons logged for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the device to reboot. |
| Mode | The reboot mode to apply; options are: "NORMAL" (standard reboot) or "FORCED" (forceful reboot). |
| Additional Body Fields | Optional additional fields to include in the request body. Currently supports: |
| - Reason | A string describing the reason for the reboot, useful for logging or auditing purposes. |
Output
The node outputs JSON data representing the response from the AvantGuard NinjaOne API after attempting to reboot the device. This typically includes status information about the reboot request, such as success confirmation or error details.
If the API returns any binary data (not indicated here), it would be included accordingly, but this node primarily deals with JSON responses.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
- Needs the base URL of the NinjaOne API configured in the credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and the provided OpenAPI specification (openapi.json) for request construction.
Troubleshooting
- Invalid Device ID: If the device identifier does not exist or is incorrect, the API will likely return an error indicating the device was not found. Verify the device ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node's credentials.
- Permission Issues: The API user must have sufficient permissions to perform device reboots. Lack of permissions will result in authorization errors.
- Network Issues: Connectivity problems to the NinjaOne API endpoint can cause timeouts or connection errors. Check network settings and firewall rules.
- Invalid Reboot Mode: Only "NORMAL" and "FORCED" modes are accepted. Providing other values will cause validation errors.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints and usage)
- n8n Documentation for guidance on setting up credentials and using HTTP/API nodes.