Einführung
Automatisierungen ermöglichen es Ihnen zu definieren, was auf einem Gerät geschehen soll, wenn bestimmte Bedingungen erfüllt sind. Ein Trigger überwacht die Bedingung — ein Zeitplan, ein Tag, eine Benachrichtigung, eine neue Registrierung. Eine Aktion (oder eine Abfolge von Aktionen) wird ausgeführt, wenn die Bedingung erfüllt ist. Sobald eine Automatisierung aktiv ist, läuft sie kontinuierlich ohne manuelle Eingriffe.
Häufige Beispiele:automatisches Patchen von Windows-Geräten nach Zeitplan, Ausführung eines Setup-Skripts bei Erkennung eines neuen Geräts oder Anwendung von Tags, wenn ein Gerät einer bestimmten Gruppe beitritt.
🎬 VIDEO
Wie Automatisierungen funktionieren
Jede Automatisierung hat zwei Teile:
Trigger— die Bedingungen, die ein Gerät in die Automatisierung bringen. Wenn ein Trigger aktiviert wird, beginnt das Gerät, die Pipeline zu durchlaufen.
Aktionen— die Schritte, die auf dem Gerät nacheinander ausgeführt werden, sobald es in die Pipeline eintritt.
Trigger und Aktionen sind unabhängig. Eine Automatisierung kann mehrere Trigger haben (jede Übereinstimmung startet die Pipeline) und mehrere Aktionen (sie werden sequenziell ausgeführt). Jede Aktion kann einzeln ein- oder ausgeschaltet werden, ohne sie aus der Pipeline zu entfernen.
Zwei Abzeichen erscheinen auf Triggern und Aktionen in der Pipeline, um zusätzliche Konfiguration auf einen Blick zu signalisieren:
IF(orange) — eine Bedingung wird auf diesen Schritt angewendet. Bei Triggern beschränkt die Bedingung, welche Geräte der Trigger abruft. Bei Aktionen steuert die Bedingung, ob die Aktion auf einem bestimmten Gerät während eines Durchlaufs ausgeführt wird.
(x)(orange) — der Schritt verwendet eine Variable, entweder durch Schreiben der Ausgabe in eine oder durch Lesen aus einer.
Trigger
Ein Trigger definiertwhen und whichGeräte, auf die eine Automatisierung abzielt. Geräte werden nicht manuell Automatisierungen zugewiesen — Trigger ziehen sie basierend auf der Bedingung automatisch ein.
Trigger-Typen umfassen Zeitpläne(täglich, wöchentlich, monatlich oder nach benutzerdefiniertem Intervall ausführen), device events (neues Gerät erkannt, Gerät tritt einer Gruppe bei oder verlässt eine Gruppe), tag events (Tag angewendet oder entfernt), data changes (benutzerdefiniertes Feld geändert), und externe Signale(webhook). Ein manueller Trigger ist auch für On-Demand-Durchläufe verfügbar.
Every trigger (except Manual) supports conditions— Filter, die einschränken, welche Geräte abgerufen werden, wenn der Trigger aktiviert wird. Bedingungen können nach Plattform, Betriebssystem, Gruppe, Tag, Status, Hostname, Gerätetyp und mehr filtern. Ohne Bedingungen gilt ein Trigger für alle Geräte in Ihrer Organisation, die der Trigger sonst abgerufen würde.
Für die vollständige Trigger-Referenz sieheAutomatisierungen → Trigger. Für Bedingungen sieheTrigger-Bedingungen.
Aktionen
Aktionen sind das, was tatsächlich auf dem Gerät ausgeführt wird. Sie werden nacheinander von oben nach unten ausgeführt. Wenn eine Aktion fehlschlägt, stoppt die Pipeline bei diesem Schritt(sofern nicht anders konfiguriert).
Verfügbare Aktionen umfassen: Ausführung von Skripten, Installation und Deinstallation von Anwendungen, Verwaltung von Betriebssystem-Updates, Neustart von Geräten, Festlegung benutzerdefinierter Felder, Anwendung oder Entfernung von Tags, Versand von Benachrichtigungen, HTTP-Anfragen und mehr.
Jede Aktion hat zwei übergreifende Optionen über ihre Kernkonfiguration hinaus:
Bedingungen— beschränkt, ob die Aktion auf einem bestimmten Gerät während eines Durchlaufs ausgeführt wird. Verwenden Sie Bedingungen, um eine Aktion basierend auf Betriebssystem, Gruppe, Tag, benutzerdefiniertem Feldwert oder dem Ergebnis einer vorherigen Aktion zu überspringen. SieheAction-Bedingungen.
Zusätzliche Optionen— Steuerelemente, die bei jeder Aktion verfügbar sind, unabhängig vom Typ: ein benutzerdefinierter Anzeigename, Fehlerverhalten (Pipeline fehlschlagen oder unterdrücken und fortfahren), Wiederholungsanzahl und die Möglichkeit, die Ausgabe der Aktion in einer Automatisierungsvariablen zu erfassen. SieheAktionsübersicht.
Für eine vollständige Referenz sieheAutomatisierungen → Aktionen.
TIPP: Level's Resource Library includes hundreds of pre-built automations you can import directly into your account — covering common use cases like patch management, new device setup, maintenance tasks, and more. Starting from a pre-built automation is faster than building from scratch.Automatisierungen
Navigate to
Automatisierungen in the sidebar to reach the automations list.HINWEIS:
New accounts include a Get Started automation group pre-populated with common automations — Windows Patching, macOS Patching, Linux Patching, Default Tags, Disk Cleanup, and others. These are fully functional automations you can enable as-is, tweak to fit your environment, or use as a reference when building your own.Each row in the table represents one automation. The columns show:Aktionen
— icons representing the trigger types and action types in use
Name — the automation name
Group — the automation group it belongs to
Last run — when the automation last fired on any device
Active runs — devices currently in the pipeline
Total runs — all-time run count across all devices
Status —
Active (has at least one active trigger) or Manual (no active triggers; only runs when manually triggered)Columns can be shown or hidden using the Columns
button in the top right.Filtering and SearchingUse the
Search
bar to filter automations by name. The Filters button opens a panel to filter by Action type oder Trigger type — useful for finding all automations that, for example, use a Run Script action or a Scheduled run trigger.Automation GroupsThe left sidebar organizes automations into groups. Groups are just for organization — they don't affect how automations run or which devices they target.
Select any group to filter the table to only automations in that group. Use
Search groups
to find a specific group by name.To move one or more automations into a group, select them using the checkboxes and click Assign to group
.TIPP: Group automations by function (e.g., Patching, Maintenance, Security) or by operating system. Either way, use a scheme that matches how your team thinks about workflows — not how Level's UI is organized.
Script RunsScript runs in the sidebar shows a filtered list of automations that Level created automatically when scripts were run ad-hoc from the device listing or device details. Each is a real automation with a Wait for approval action and a Run script action — they behave exactly like any other automation.
For a full explanation of how script run automations are created and used, see
Scripting Overview.
New Automations and Archived AutomationsNew automations in the sidebar shows automations that were created in the last 7 days.
Archived automations
shows automations that have been archived. Archived automations don't run (triggers are disabled); they can be restored at any time.Creating an Automation
Click + Create automation
in the top right of the automations list.
Enter a name for the automation.Click Create
.
HINWEIS: A newly created automation has no triggers and no actions. It won't run until you add at least one trigger. Until then, it shows a Manual
action and can only be run by manually adding devices.Inside an AutomationClicking any automation in the list opens its pipeline view.View Mode and Edit ModeBy default, automations open in
View mode
. In view mode, you can see the pipeline and toggle individual triggers and actions on or off. You can't add, remove, or reorder steps.
Clicking any trigger or action in view mode opens a detail panel on the right showing two things: the step's full configuration, and a
Recent devices list showing which devices have recently passed through that step along with their run status and duration.From the Recent devices list, you have two ways to dig deeper:
Click the > (caret) next to a device to expand it inline and see the
Output
und Input tabs for that step — the actual text output the action produced on that device.Click the → (arrow) to navigate to the full run detail for that device, showing all steps in the pipeline, their individual statuses, durations, and output.HINWEIS:
Triggers have a Run trigger now button in their detail panel. This fires the trigger immediately on all currently matching devices without waiting for the next scheduled run — useful for testing or for one-off manual execution of a scheduled automation.
Click Bearbeiten in the top right to switch to Edit mode. In edit mode:
Add triggers using the + button in the trigger areaAdd actions using the +
button between or below existing actionsReorder actions by dragging the handle on the left side of any action stepEdit a trigger or action by clicking it to open the configuration panel
Changes to each step are saved per-step (save inside the panel), not globallyClick Done
to exit edit mode.
HINWEIS:
Triggers can't be reordered because order is irrelevant — any matching trigger starts the pipeline. If you have multiple triggers, any one of them firing is enough to start a run for a matching device.
VariablenThe Variablen
tab (in the left panel) lists the automation variables defined for this automation.Automation variables pass data between steps. An action can write a value to a variable — for example, capturing a script's exit code or a custom field value — and a later action (or an action condition) can read that value to branch or filter behavior. Variables are defined per automation and are only accessible within that automation.Beyond automation variables, Level also makes system variables available in every automation — things like device name, OS, IP address, and group. These don't need to be defined; they're always present.
For the full reference on creating and using variables, see
Automation Variables und System Variables
.
Verlauf
The Verlauf tab shows every device that has run through this automation — one row per run, with the device name, trigger event, status, and start time. Use the search bar or Filter by status to narrow the list.
Clicking a row opens a run detail panel on the right showing:
Run details — source (what triggered the run), start time, end time, total duration, and overall statusWorkflow progress — each action step with its individual duration and status (Success, Skipped, Failed)Click the
>
next to any step in Workflow progress to expand it and see that step's full output and input inline.A
Erneut ausführen button appears in the top right of the run detail panel, and also as a bulk action in the history table toolbar. Rerun is a dropdown with two options:
Erneut ausführen — restarts the pipeline from the beginning for that deviceRetry from failed
— resumes from the step that failed, skipping the steps that already succeededHINWEIS: You can also reach a specific device's run detail from the pipeline view. When you click a trigger or action step in view mode, the Recent devices list shows recent runs for that step. Clicking the arrow
→ on any device row navigates to the full run detail for that device.
Active DevicesThe bottom of the left sidebar shows a live count of devices currently in the pipeline, broken down by state:
Running, Waiting on approval, and When next online
. Click
View all to see which devices are in each state.Running an AutomationAutomations with active triggers run automatically — no manual step required. But there are several ways to trigger a run on demand or add specific devices to a pipeline manually.From the automation pipeline — click + Add a device in the trigger area to manually push one or more devices into the pipeline immediately, bypassing trigger conditions.From the device listing
— select one or more devices, open the
Aktionen
menu, and choose Run automation. Select which automation to run. The selected devices enter that automation's pipeline directly.From device details
— same Aktionen menu is available on an individual device's detail page.From the trigger panel — in view mode, click a trigger to open its detail panel and use Run trigger now
to fire it immediately against all currently matching devices.From alerts — automations can be triggered by monitor alerts via the Remediation trigger type. When a monitor fires an alert, any automation using that alert as a trigger runs automatically on the affected device.Watching a Run in Progress
Once a device enters the pipeline, Level tracks it in real time.On the pipeline view:A device icon appears next to the trigger that pulled it in, then moves through the pipeline as each action executesThe
Active devices count in the bottom left increments and shows how many devices are currently Running, Waiting on approval, or queued for When next online
Clicking a device in the Active devices panel (or in an action step's detail panel) opens the live run detail, where the Output tab streams action output as it arrives
HINWEIS:
If a device is offline when a trigger fires, it enters a
When next online
queue. The run resumes from the beginning when the device checks back in — unless you've added a Status = Online trigger condition to exclude offline devices entirely.Global HistorySelecting
Verlauf
in the main sidebar opens a cross-automation run history — every automation run across your entire account in one view.Columns include device name (with group path), automation name, trigger event, status, and start time. Filter by status to isolate failed runs, or search by device or automation name. Export to CSV exports the current filtered view.Selecting a row opens the same run detail panel as in the per-automation history tab — source, timestamps, total duration, overall status, and per-step Workflow progress with expandable output.
The
Erneut ausführen dropdown is also available here, letting you rerun or retry-from-failed across multiple selected rows in bulk.FAQ
What's the difference between an Active and Manual automation? Active means the automation has at least one enabled trigger — it's watching for matching devices and will fire on its own. Manual means there are no active triggers; the automation only runs when you manually add a device to the pipeline.Can an automation target specific devices or groups?
Automations don't get assigned to devices or groups directly. Triggers define which devices are pulled in. All triggers include optional conditions (OS, group, tag, custom field) to narrow the target set. For example, a Scheduled trigger with a condition of "Group = Windows Servers" will only run on devices in that group.
Can the same device be in an automation's pipeline more than once at the same time? No — a device can only have one active run per trigger at a time. If a device is already in the pipeline (running, waiting for approval, or queued as "when next online"), a subsequent firing of the same trigger won't add it again. The duplicate is silently dropped. Once the current run completes, the device can be pulled in again by the next trigger firing. Note that this is per trigger: if an automation has two different triggers, a device could technically have one active run from each — but the same trigger won't create a second.What happens if an action fails mid-pipeline?
The run stops at the failed step. The device remains in the pipeline history with a failed status. You can rerun from the failed step — click the row in the
Verlauf tab to open the run detail, then click
Erneut ausführen. You don't have to restart from the beginning.
Who can create and manage automations? Access is controlled by the permissions set for each device group. Technicians need the appropriate permission level to create automations, run them, or view history. See
Arbeitsbereich → Berechtigungen for details.Can I run an automation immediately without setting up a trigger? Yes. Use a Manual trigger, or just create the automation without a trigger and add devices to the pipeline manually from the automation's pipeline view or from the
Aktionen menu on the device listing.Where can I find pre-built automations? Level's
Resource Library has pre-built automations, monitors, and scripts. Import directly into your account with one click.Manual trigger, or just create the automation without a trigger and add devices to the pipeline manually from the automation's pipeline view or from the Actions menu on the device listing.
Where can I find pre-built automations? Level's Resource Library has pre-built automations, monitors, and scripts. Import directly into your account with one click.