Automations
Turn recurring operations into governed workflows.
Automations turn repeatable operational work into managed workflows. Instead of relying on manual technician steps, Breeze can execute predefined actions when schedules match, events occur, webhooks arrive, or operators trigger runs explicitly.
Trigger and Action Model
Automations support four trigger modes:
- schedule
- event
- webhook
- manual
Actions can run scripts, execute commands, create alerts, or send notifications. This gives teams enough flexibility to automate routine remediation and coordination workflows without custom glue code.
Policy-Driven Configuration
Automation definitions are managed through Configuration Policies. That means automation behavior can inherit across organization, site, and group scope using the same hierarchy model as other platform controls.
This is especially useful for MSPs that need consistent baseline workflows with per-customer overrides.
Run Outcomes and Failure Handling
Runs are tracked as running, success, failed, or partial. Failure behavior can be configured to stop, continue, or continue with notification, depending on how critical the workflow is.
Why Teams Use It
Automations reduce repetitive toil, improve response consistency, and make operational behavior more auditable by moving recurring playbooks into structured, policy-managed execution.
Capabilities
Multiple Trigger Modes
Automations can run on schedules, platform events, inbound webhooks, or manual invocation.
Policy-Based Definitions
Automation configuration is managed through Configuration Policies for inheritance-aware scoping.
Operational Action Set
Actions can execute scripts, run commands, create alerts, and send notifications.
Run Outcome Tracking
Run records capture success, partial success, and failure behavior with configurable on-failure policy.