Every automation will have this trigger (whether selected or not). This means that devices can be manually added to any automation pipeline. This trigger has no editable parameters.

There are three types of scheduled triggers: Daily, Weekly, and Monthly. These triggers match devices at recurring intervals, whether on a daily, weekly, or monthly frequency. Additionally, each trigger includes a conditions section where device attributes can be used to narrow down the scope and refine the matching criteria.

This trigger will detect when an agent has been installed on a new device and it has checked in to Level. This trigger will wait for 1 minute before adding the device to the automation in order to give the new device enough time to report on all of its characteristics.

This is useful for assigning tags as soon as a device checks in, or checking for security posture once a device goes into management.

This trigger will detect when a device has been added to a Level group. This is useful when organizing agents into departments, or clients. This way when a device is moved to a department or client folder, then certain applications could be installed, or other required settings could be applied.

This is the opposite of Device Enters Group, when a device is removed from a Level folder this trigger will be matched. This is useful if devices need to be off boarded once removed from a department or client group. Software, settings, and credentials could be removed.

This trigger will match when a Level tag is added to a device. This is useful when tags are used to deploy specific software. For example, when the "Office" tag is applied to a device, then install Office! Only one tag can be chosen per condition.

Just like the Tag Applied trigger this will match devices when a Level tag is removed from a device. An example use case would be when a licensed software tag is removed from the device, that the action of the automation could be to uninstall the software.

A web hook will trigger when the URL is accessed. Upon saving a web hook trigger, a random URL will be generated. An optional (but recommended) option to require an authorization header is also available to ensure that the URL is not accessed by unauthorized parties. The condition field is required to determine which agents should be added to the automation pipeline.

This is useful for integrating other tools into Level. For example a ticketing system could trigger diagnostics on devices.