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 → Create Policy
AI-generatedOverview
This node integrates with the NinjaOne API to manage policies within the "Management" resource. Specifically, the "Create Policy" operation allows users to create new policies in different modes (new, child, or copy) and configure various attributes such as name, description, node class, and enabled status.
Use cases include automating policy creation workflows for IT asset management, security compliance, or configuration management across diverse device types and environments. For example, an IT administrator can use this node to programmatically create a new Windows Server policy or clone an existing policy as a child policy, streamlining policy deployment at scale.
Properties
| Name | Meaning |
|---|---|
| Mode | Policy creation mode. Options: NEW, CHILD, COPY |
| Template Policy Id | Identifier of the template policy used when creating a policy (number). |
| Parent Policy Id | Identifier of the parent policy if creating a child policy (number). |
| Name | The name of the policy (string). |
| Description | A textual description of the policy (string). |
| Node Class | The classification of nodes/devices the policy applies to. Options include WINDOWS_SERVER, LINUX_SERVER, MAC, ANDROID, various NMS device types, etc. |
| Enabled | Boolean flag indicating whether the policy is enabled or disabled. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to create the policy. This typically includes details of the newly created policy such as its ID, status, and other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for authenticating with the NinjaOne API.
- The node uses the NinjaOne REST API endpoints under
/v2/policiesfor policy management. - Proper network access and permissions to the NinjaOne API are necessary.
Troubleshooting
- Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid or incomplete property values (e.g., missing required fields like
name) may result in API errors. - Using an unsupported
modeor mismatchedtemplatePolicyId/parentPolicyIdcombinations could cause request rejections.
- Error messages:
- Errors from the NinjaOne API will be surfaced in the node output under an error object if "Continue On Fail" is enabled.
- Typical errors include HTTP 400 for bad requests, 401 for unauthorized access, and 404 if referenced policies do not exist.
- Resolution tips:
- Verify all required properties are set correctly.
- Ensure the API credential is valid and has sufficient permissions.
- Check that referenced IDs (template or parent policy) exist and are accessible.
Links and References
- NinjaOne API Documentation (for detailed API endpoint info)
- n8n OAuth2 Credential Setup (for configuring API authentication)