Skip to content

Automations ​

Automations start jobs on a schedule or in response to an event. Configure endpoint automations on the relevant tenant, folder, group, or endpoint. Configure infrastructure automations on the job itself.

Endpoint Time Automations ​

Choose the job, target scope, schedule, and timezone. Use a recurring cron schedule for maintenance or a one-time schedule for a rollout.

Enable Run on next connect if missed when offline devices should catch up. One run waits for the endpoint; repeated missed times do not create a backlog. Editing or disabling the automation clears a deferred run.

Job validity windows and endpoint-specific disables still apply.

Endpoint Event Automations ​

Choose an event that corresponds to the work: for example, initial enrollment, connection, system boot, a Windows user logon, an activated alert, or completion of another job. Select the relevant source job, alert, or integration where required.

Set order when several automations share an event. A random delay spreads work when many endpoints trigger together.

Windows logon and logoff events represent actual console or RDP sessions, not lock/unlock or RDP reconnection. A boot trigger requires the Agent to report the new boot. Do not rely on offline events being replayed later.

Use Webhooks for external HTTP triggers and SNMP trap triggers for network-device events.

Assignment automation behavior ​

Enable Run when assigned on an endpoint job's Automations tab for work that should start when the job first becomes assigned to a device. Overlapping assignments do not start duplicate runs. Existing assignments do not run retroactively when this option is enabled.

Removing all assignments and assigning the job again can start it again. Normal job eligibility still applies; a blocked assignment event is not saved for a later retry.

Infrastructure Job Automations ​

Open an infrastructure job's Automations tab to configure automatic runs:

TriggerUse it for
TimeA recurring or one-time maintenance schedule.
Job completedA follow-up infrastructure job after selected outcomes of the source job.
Git changesBuild changed repository branches.
Webhook receivedWork requested by a configured infrastructure webhook.
Windows update approvedPreparing update content after approval in enabled rings.

For approval triggers, use the delay to combine approvals arriving together. An active run can have one combined follow-up. Revoking an approval during the delay does not cancel the pending run, so the job must use current approvals when selecting work.

Infrastructure validity windows apply to automated starts. Jobs that use Runner tasks need an eligible Runner in the configured pool.

Where To Manage Them ​

Inspect an endpoint's Jobs view to understand why work is scheduled for that device. Edit inherited automations at their source scope. Assignment automations belong to the endpoint job; infrastructure automations belong to the infrastructure job.

Configuration Profiles have separate assignment automations.

Trigger values ​

Jobs can read event context through the trigger variables. Automated starts use configured persistent values and do not ask for interactive launch inputs.

Webhook conditions ​

For Webhook received automations, add optional conditions to select which requests start the job. Each automation has its own conditions, even when several automations share a webhook. See Filter requests for configuration and examples.