Introduction
The new device detected trigger fires when a device checks into Level for the first time. Use it to automate provisioning tasks — installing software, applying configuration, running baseline scripts — as devices enroll without any manual intervention.
ℹ️ NOTE: Adding non-manual triggers requires either admin status or a role with the Manage automations permission. If you can see the automation but can't add triggers, check your role's permissions with your admin. See Workspace → Permissions for details.
New Device Detected Trigger
This trigger has no base configuration options — there's nothing to schedule or specify beyond the condition and additional options.
Condition
You must select a condition to save the trigger. Choose All devices to fire for every new device that enrolls, or narrow the scope with conditions like Platform or Group.
For the full condition reference, see Trigger Conditions.
Additional Options
Expand Additional options to set an optional Trigger name and toggle the trigger on or off with the Enabled switch.
Trigger name — Replaces the default label on the pipeline trigger card.
Enabled — When off, the trigger won't fire. In-progress runs are unaffected.
FAQ
Does this trigger fire every time a device comes online, or only the first time? Only the first time a device checks into Level. Subsequent connections from the same device won't re-fire it.
What happens if a device is re-enrolled after being removed from Level? This depends on whether Level recognizes the device as the same one or treats it as new. Confirm with your admin or Level support if predictable behavior here matters for your provisioning workflow.
Who can add or edit triggers on an automation? Admin users can always add triggers. Non-admin users need the Manage automations permission on their role, plus access to the automation's group. If an automation has no triggers yet, any user with group access can add the first one.