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 Custom Fields Policy Condition
AI-generatedOverview
This node integrates with the NinjaOne API to manage policy conditions related to custom fields within the Management resource. Specifically, the "Create Custom Fields Policy Condition" operation allows users to create a new condition for a given policy by specifying various parameters such as severity, priority, notification settings, and matching criteria.
Use cases include automating the creation of policy conditions that trigger alerts or actions based on custom field values in your managed environment. For example, you might create a condition that triggers a critical alert when a custom field meets certain criteria, enabling proactive incident management.
Properties
| Name | Meaning |
|---|---|
| Policy Id | The unique identifier of the policy to which the custom fields condition will be added. |
| Enabled | Boolean flag indicating whether the policy condition is active (true) or inactive (false). |
| Display Name | A descriptive name for the policy condition to identify it easily. |
| Severity | The severity level of the policy condition. Options: NONE, MINOR, MODERATE, MAJOR, CRITICAL. |
| Priority | The priority level of the policy condition. Options: NONE, LOW, MEDIUM, HIGH. |
| Channels | JSON array defining notification channels for the policy condition. |
| Scripts | JSON array defining scripts associated with the policy condition, including execution context and variables. |
| Notification Action | Defines the notification action to take. Options: NONE, SEND. |
| Notify On Reset | Boolean flag indicating if notifications should be sent when the condition resets. |
| Reset Threshold | Number representing the reset threshold in seconds for the policy condition. |
| Match All | JSON array of conditions where all must be met by the custom field value. |
| Match Any | JSON array of conditions where any one must be met by the custom field value. |
Output
The node outputs an array of JSON objects representing the response from the NinjaOne API after creating the custom fields policy condition. Each output item contains the full JSON response returned by the API, which typically includes details about the newly created condition such as its ID, status, and configuration.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n for authenticating requests to the NinjaOne API.
- The node uses OAuth2 authentication under the generic term "an API key credential".
- Network access to the NinjaOne API endpoints is necessary.
Troubleshooting
- Missing or invalid Policy Id: Ensure the Policy Id property is set correctly and corresponds to an existing policy in NinjaOne.
- Invalid JSON in Channels, Scripts, Match All, or Match Any: These properties expect valid JSON arrays. Invalid JSON syntax will cause errors. Validate JSON formatting before use.
- Binary Data Errors: Not applicable for this operation since it does not handle binary data.
- API Authentication Failures: Verify that the API key credential is properly configured and has sufficient permissions.
- Error Messages:
- "No binary data exists on item!" or "No binary data property ... does not exist on item!" — Not relevant here but may appear if other operations expecting binary data are used incorrectly.
- General API errors will be returned in the JSON output under an error message if "Continue On Fail" is enabled.
Links and References
- NinjaOne API Documentation
- n8n Documentation on Creating Custom Nodes
- JSON Validator – Useful for validating JSON input properties like Channels, Scripts, Match All, and Match Any.