AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node operation allows users to create a custom fields policy condition within a management system. It is useful for defining specific conditions that trigger policies based on custom field values, enabling fine-grained control over policy enforcement and notifications. For example, an IT administrator could use this to set up a policy condition that triggers alerts when certain device attributes meet specified criteria, such as severity or priority levels.

Properties

Name Meaning
Policy Id The unique identifier of the policy to which the custom fields condition will be added.
Additional Body Fields Optional additional settings for the policy condition:
- Enabled Whether the policy condition is active (true/false).
- Display Name A human-readable name for the policy condition.
- Severity The severity level of the condition; options: NONE, MINOR, MODERATE, MAJOR, CRITICAL.
- Priority The priority level of the condition; options: NONE, LOW, MEDIUM, HIGH.
- Channels JSON array specifying notification channels for the condition.
- Scripts JSON array defining scripts associated with the condition, including execution context.
- Notification Action Action to take for notifications; options: NONE, SEND.
- Notify On Reset Whether to notify when the condition resets (true/false).
- Reset Threshold Time in seconds before the condition can reset. Default is 14400 seconds (4 hours).
- Match All JSON array of conditions all of which must be met by the custom field value.
- Match Any JSON array of conditions any of which must be met by the custom field value.

Output

The node outputs a JSON object representing the created custom fields policy condition. This typically includes details such as the assigned policy ID, condition parameters, and status. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The base URL for the API is configured via credentials.
  • Uses an OpenAPI-based client internally to interact with the external service's API.

Troubleshooting

  • Missing or invalid Policy Id: Ensure the Policy Id is provided and valid; otherwise, the API call will fail.
  • Invalid JSON in Channels, Scripts, Match All, or Match Any: These fields require valid JSON input; malformed JSON will cause errors.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network or API errors: Check connectivity and API endpoint availability.

Links and References

  • Refer to the external service's API documentation for detailed information on policy conditions and their parameters.
  • JSON formatting tools may help prepare complex JSON inputs for fields like Channels, Scripts, Match All, and Match Any.

Discussion