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 → Node Approval Operation
AI-generatedOverview
This node enables users to perform approval or rejection actions on devices within a management system via the NinjaOne API. Specifically, it supports a "Node Approval Operation" under the "Management" resource, allowing automated workflows to approve or reject device-related requests or statuses.
Common scenarios include:
- Automatically approving new devices added to a network.
- Rejecting devices that do not meet compliance criteria.
- Integrating device approval workflows into larger IT automation processes.
For example, an IT admin could set up a workflow where devices pending approval are automatically approved or rejected based on predefined conditions, streamlining device management and reducing manual intervention.
Properties
| Name | Meaning |
|---|---|
| Mode | The approval action to perform. Options: APPROVE or REJECT. |
| Devices | A JSON array representing the devices to which the approval action will be applied. |
Output
The node outputs a JSON object containing the response from the NinjaOne API after performing the approval or rejection operation. This typically includes details about the success or failure of the request and any relevant data returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured in n8n credentials to authenticate with the NinjaOne API.
- Depends on the NinjaOne API being accessible and properly configured for the user’s account.
- Uses the
n8n-openapi-nodepackage internally to build and send requests.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Malformed JSON in the Devices property may lead to parsing errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"No binary data exists on item!"or similar errors related to binary data do not apply here since this operation does not handle binary inputs.- API error responses will be included in the output JSON under an
errorfield if the node is set to continue on failure.
Resolutions:
- Ensure the API key or OAuth2 token is correctly set up in n8n credentials.
- Validate the JSON format of the Devices input before running the node.
- Check network access and NinjaOne API status.