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 facilitates managing approval actions on nodes within a system, specifically allowing users to approve or reject nodes. It is useful in workflows where automated or manual validation of nodes is required before proceeding with further processing. For example, in IT management or security automation, this node can be used to programmatically approve or reject device nodes based on certain criteria or human input.
Properties
| Name | Meaning |
|---|---|
| Mode | The approval action to perform. Options: "APPROVE" to approve the node, "REJECT" to reject it. |
| Additional Body Fields | Optional additional fields to include in the request body. Currently supports: - Devices: JSON array specifying devices related to the approval operation. |
Output
The node outputs JSON data representing the result of the approval operation. This typically includes confirmation of the action taken (approved or rejected) and any relevant metadata returned by the API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authentication with the AvantGuard NinjaOne service.
- Depends on the external AvantGuard NinjaOne API endpoint specified by the base URL in credentials.
- Uses the
@avantguardllc/n8n-openapi-nodepackage for OpenAPI integration. - Requires proper configuration of the API base URL and authentication credentials in n8n.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect JSON format in the "Devices" field under Additional Body Fields may cause request errors.
- Selecting an unsupported mode value (other than APPROVE or REJECT) will likely cause the node to fail.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- JSON parsing errors for the Devices field suggest malformed JSON input; ensure valid JSON syntax.
- API response errors may indicate permission issues or invalid resource identifiers; check API permissions and inputs.
Links and References
- AvantGuard NinjaOne API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Nodes
- JSON Syntax Guide