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 → Cancel Device Maintenance
AI-generatedOverview
This node integrates with the NinjaOne API to perform various management tasks. Specifically, for the "Management" resource and the "Cancel Device Maintenance" operation, it allows users to cancel scheduled maintenance on a device by specifying the device's identifier. This is useful in IT management scenarios where planned maintenance needs to be aborted or rescheduled due to changing priorities or issues.
Practical example: An IT administrator can automate the cancellation of maintenance windows on devices if an urgent update or patch needs to be applied immediately, avoiding downtime caused by the original maintenance schedule.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the device for which the maintenance cancellation is requested. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to cancel the device maintenance. The structure depends on the API's response but generally includes confirmation of the cancellation or error details.
No binary data output is involved in this operation.
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 under
/v2/paths. - No additional external dependencies beyond the NinjaOne API and n8n's HTTP request helpers.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent device ID will likely result in an error from the API.
- Missing or expired API authentication tokens will cause authentication failures.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors returned from the API are passed through in the JSON output under an
errorfield if "Continue On Fail" is enabled. - If no binary data is found when expected (not applicable here), the node throws a specific error.
- Errors returned from the API are passed through in the JSON output under an
Resolutions:
- Verify the device ID is correct and exists in NinjaOne.
- Ensure the OAuth2 credentials are valid and refreshed.
- Check network connectivity and firewall settings.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring API authentication)