Guide

What Are The Available Triggers For Automations

Manually

Selecting this method allows you to trigger the automation manually. Once you have selected this method, you will then need to select the Service and Object for which the automation will run.

Manually triggered automation can be repeatedly used without limitations on the number of times the automation can be triggered. This automation needs to be triggered on the same entity that is set in the automation.
Use this option when you want to test the automation actions or only want to trigger the automation once. It will run for the only entity object from which it is triggered, which allows you more control over the variable for testing purposes.

On Schedule

Selecting this method allows you to schedule the automation to run periodically. Once you have selected this method, you will then need to select whether this is to run on a “PolicyViolation” or “Inventory Item”. If you choose “Policy Violation”, you then need to specify the policy for the trigger. After choosing “Inventory Item”, you then need to choose the Service and object Entity for the trigger.

Next, you will need to select the period this can be Day, Week, Month Year. selecting

  • Day - Choosing Day allows you to specify the day of the week for the trigger to run. You can also specify if it is every day or a given day by choosing 1 to 99.
  • Week - Choosing Week allows you to specify the day(s) for the trigger to run. You can also specify if it is every week or every selected number of weeks by choosing 1 to 4.
  • Month - Choosing Month allows you to specify either the date for the trigger to run in the month, or by specifying the First, Second, or Third day in the month, and how often the month triggers by selecting 1 to 12.
  • Year - Choosing Year allows you to either specify a particular date for the trigger to run or the First, Second, Third, or Fourth day of a given month. It is also possible to specify how often the trigger runs a year by selecting 1 to 10 years.
Using "On Schedule" means that the object violation will have the automation actioned every time. This means any changes made to the actions of the automation will be updated to all violations in a policy. Use this option if you want to keep actioning the automation until it is no longer a violation.

On Policy Violation

Selecting this method allows you to set the automation to run on/after every violation for a given Policy. Choosing this option, you will then need to specify the policy. The Automation will then be triggered after the next scan of the service that the policy object is set to.

Using "On Policy Violation" means that the object violation will have the automation actioned every time. This means any changes made to the actions of the automation will be updated to all violations in a policy. Use this option if you want to keep actioning the automation until it is no longer a violation.
"Policy violation"  automation depend on a scan and can be started only after the scan. If your scan for the object is set to run monthly, then the automation will only be triggered monthly.

Last updated: 8/5/2025