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
Backup → Submit Integrity Check Job
AI-generatedOverview
This node integrates with the NinjaOne API to submit an integrity check job for a specified backup device and plan. It is useful in scenarios where you want to programmatically trigger data integrity verification on backup devices managed by NinjaOne, ensuring backups are consistent and reliable.
For example, an IT administrator can use this node within an automation workflow to regularly submit integrity check jobs for backup devices, helping maintain data health without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Device Id | The numeric identifier of the backup device on which to run the integrity check job. |
| Plan Uid | The unique string identifier of the backup plan associated with the integrity check job. |
Output
The node outputs JSON data representing the response from the NinjaOne API after submitting the integrity check job. This typically includes details about the job submission status or any relevant metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- Depends on network connectivity to the NinjaOne API endpoint.
- Uses the NinjaOne API version as defined in the bundled OpenAPI specification.
Troubleshooting
Common issues:
- Invalid or missing Device Id or Plan Uid parameters may cause the API request to fail.
- Authentication errors if the NinjaOne API credentials are not properly set up or expired.
- Network connectivity problems preventing access to the NinjaOne API.
Error messages:
- Errors returned from the NinjaOne API will be included in the node output if "Continue On Fail" is enabled.
- If binary data is expected but missing (not applicable here), the node would throw an error.
- General HTTP errors such as 401 Unauthorized or 404 Not Found indicate credential or resource identification issues.
To resolve these:
- Verify that Device Id and Plan Uid are correctly provided.
- Ensure the NinjaOne API credentials are valid and have necessary permissions.
- Check network access to the NinjaOne API endpoints.
Links and References
- NinjaOne API Documentation (general reference)
- n8n documentation on OAuth2 Credentials
- n8n community forums for NinjaOne integration discussions