Introducción
Every scheduled and event-based trigger supports conditions. Condiciones filter which devices are pulled into an automation run when the trigger fires — so instead of running against every assigned device, you can target a specific subset of devices based on platform, group, tag, status, or other device attributes.
The manual trigger doesn't support conditions. All other trigger types share the same condition builder described here.
How Condiciones Work
Condiciones are configured per trigger, not per automation. If an automation has multiple triggers, each trigger can have its own independent condition set.
When a trigger fires, Level evaluates its conditions against your devices at that moment. Devices that match all conditions are pulled into the automation run. Devices that don't match are skipped — they're not tracked or queued, and they'll be evaluated fresh the next time the trigger fires.
Multiple conditions use AND logic: every condition must be satisfied for a device to be included. There's no OR option within a single trigger. If you need OR-style behavior, add a second trigger with different conditions.
ℹ️ NOTA: Triggers evaluate against all devices in your organization. The Grupo condition is how you scope a trigger to a subset — without one, any device in the org that matches the other conditions will be pulled in.
Configuración de condiciones
Condiciones are set inside the trigger configuration panel when adding or editing a trigger.
ℹ️ NOTA: Triggers and actions are only editable in edit mode. From the pipeline view, click Editar in the top-right corner to enter edit mode. If you click a trigger or action outside of edit mode, a read-only detail panel opens showing run status and history — you won't see configuration options there.
Open the trigger configuration panel by clicking an existing trigger or adding a new one.
Click the Condición dropdown and select a condition type.
Set the operator and value for the condition.
To add another condition, click + Add new condition.
To remove a condition, click Eliminar next to it.
Click Guardar to apply.
Referencia de condiciones
ℹ️ NOTA: Several condition types — including Plataforma, SO, Etiqueta, and Grupo — are populated dynamically from your actual device inventory. If your environment only has Windows devices, you'll only see Windows in the Plataforma dropdown. SO shows the specific versions present across your enrolled devices. Empty dropdowns mean Level hasn't detected any devices with that attribute yet.
All devices
No filtering applied. Every device in your organization is included when the trigger fires.
Selecting All devices requires no further configuration. Use it when you want the trigger to run against your entire device inventory with no restrictions.
Plataforma
Filtra por la familia del sistema operativo del dispositivo.
Operador | Descripción |
Igual a | El SO del dispositivo coincide con una de las plataformas seleccionadas |
No igual a | El SO del dispositivo no coincide con ninguna de las plataformas seleccionadas |
Valors: Windows, macSO, Linux. Multiple values can be selected.
Etiqueta
Filtra por las etiquetas aplicadas al dispositivo.
Operador | Descripción |
Igual a | El dispositivo tiene todas las etiquetas seleccionadas |
No igual a | El dispositivo no tiene ninguna de las etiquetas seleccionadas |
Selecciona una o más etiquetas de la lista de etiquetas de tu organización.
💡 CONSEJO: Etiqueta conditions are useful for targeting devices by function or client without relying on group structure — for example, running a trigger only on devices tagged SERVER or PRODUCTION.
Grupo
Filtra por el grupo de dispositivos al que pertenece el dispositivo.
Operador | Descripción |
Igual a | El dispositivo es miembro de uno de los grupos seleccionados |
No igual a | El dispositivo no es miembro de ninguno de los grupos seleccionados |
Selecciona uno o más grupos de tu jerarquía de grupos. Child groups can be expanded inline.
Estado
Filter by whether the device is currently online or offline at the moment the trigger fires.
Operador | Descripción |
Igual a | El estado del dispositivo coincide con el valor seleccionado |
No igual a | El estado del dispositivo no coincide con el valor seleccionado |
Valors: Online, Offline.
ℹ️ NOTA: The Estado condition is the key lever for controlling offline device behavior. Without a Estado condition, offline devices that otherwise match will be pulled into the run and queued — they'll resume at whatever action they were on once they come back online. Adding a Estado = Online condition excludes offline devices entirely, so they won't be queued at all.
Nombre de host
Filtra por el nombre de host del dispositivo.
Operador | Descripción |
Igual a | Nombre de host exactly matches the entered value |
No igual a | Nombre de host does not match the entered value |
Contiene | Nombre de host includes the entered string |
No contiene | Nombre de host does not include the entered string |
Introduce el valor del nombre de host manualmente. La coincidencia no distingue entre mayúsculas y minúsculas.
💡 CONSEJO: Use Contiene to target naming conventions — for example, filtering to all devices whose hostname contains SRV or a client prefix.
Visto por última vez (en días)
Filtra por cuántos días han pasado desde que el dispositivo se registró por última vez con Level.
Operador | Descripción |
Mayor que | El dispositivo fue visto por última vez hace más de N días |
Mayor que or equal to | El dispositivo fue visto por última vez hace N o más días |
Menor que | El dispositivo fue visto por última vez hace menos de N días |
Menor que or equal to | El dispositivo fue visto por última vez hace N días o menos |
Introduce un número entero de días como valor de texto libre.
💡 CONSEJO: Use this condition to limit automation runs to recently active devices — for example, skipping devices that haven't been seen in more than 30 days, which may be decommissioned or in storage.
Arquitectura
Filtra por la arquitectura de CPU del dispositivo.
Operador | Descripción |
Igual a | La arquitectura del dispositivo coincide con el valor seleccionado |
No igual a | La arquitectura del dispositivo no coincide con el valor seleccionado |
Valors: amd64, arm64.
SO
Filter by the device's specific SO version.
Operador | Descripción |
Igual a | SO version matches the selected value |
No igual a | SO version does not match the selected value |
Valors are populated from the SO versions present in your device inventory. Examples include Windows 11, Windows 10, Windows Server 2022, Windows Server 2019, Windows Server 2016, macSO Sonoma, Debian. Your list will reflect what's actually enrolled.
ℹ️ NOTA: SO values are specific version names, not SO families. To filter broadly by operating system type (Windows, macSO, Linux), use the Plataforma condition instead.
Tipo
Filtra por tipo de dispositivo.
Operador | Descripción |
Igual a | El tipo de dispositivo coincide con el valor seleccionado |
No igual a | El tipo de dispositivo no coincide con el valor seleccionado |
Valors: Workstation, Server.
Preguntas frecuentes
Do conditions apply every time the trigger fires, or just the first time? Every time. Condiciones are evaluated fresh on each trigger fire. A device that matched last week might be excluded this week if its group membership, tags, or status has changed.
Can I use OR logic between conditions? Not within a single trigger. Multiple conditions always use AND logic. To achieve OR-style behavior, add a second trigger to the automation with different conditions — both triggers will be evaluated independently.
Will a device be skipped permanently if it doesn't match the conditions? No. Condiciones are evaluated fresh each time the trigger fires. If a device's attributes change — its group, tags, status, or SO — and it matches on the next fire, it'll be included in that run.
What if I want to run a trigger on all devices except those in one group? Use a Grupo condition with the No igual a operator and select the group to exclude.
Can I use conditions to filter devices on the manual trigger? No. The manual trigger doesn't support conditions — you select devices directly when adding them. See Manual Trigger for how that works.