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 → Update Device Maintenance
AI-generatedOverview
This node integrates with the NinjaOne API to update device maintenance settings. Specifically, it allows users to set a maintenance window for a device by specifying start and end times, and to disable certain features during this maintenance period. This is useful in IT management scenarios where devices need scheduled downtime for updates or repairs without triggering alerts or interfering with normal operations.
Practical examples include:
- Scheduling a maintenance window for a server to apply patches.
- Temporarily disabling monitoring features on a workstation during hardware upgrades.
- Automating maintenance periods across multiple devices via workflow.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device to update maintenance for. |
| Disabled Features | A JSON array listing features that will be disabled during the maintenance window. |
| Start | Timestamp (number) indicating when the maintenance window starts; optional, defaults to now if not set. |
| End | Timestamp (number) indicating when the maintenance window ends. |
Output
The node outputs a JSON object representing the response from the NinjaOne API after updating the device maintenance. This typically includes confirmation details about the updated maintenance window and the disabled features.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the NinjaOne API.
- The node uses the NinjaOne OAuth2 API credentials for authenticated requests.
- No additional external dependencies are required beyond the NinjaOne API access.
Troubleshooting
Common issues:
- Invalid or missing device Id can cause the API call to fail.
- Incorrectly formatted JSON in "Disabled Features" may lead to parsing errors.
- Providing an end time earlier than the start time could result in API rejection.
- Missing or expired API authentication token will cause authorization errors.
Error messages and resolutions:
"No binary data exists on item!"— Not applicable here since this operation does not use binary data.- API error responses related to invalid parameters should be checked against the input values.
- Authentication errors require verifying the API key or OAuth2 token validity and permissions.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation on Credentials (for setting up API authentication)