Introduction
Installs one or more applications on a device using winget package IDs. Good for deploying standard software to new devices or ensuring specific apps are present across your environment.
Install Winget Package
Open an automation and add a new action step.
Under App management, select Install winget package.
In the Package(s) field, enter the winget package ID for each app you want to install. Press
Tabor type a comma to add additional packages.Click Save.
ℹ️ NOTE: The Package(s) field is required. You can't save the action without at least one package ID.
💡 TIP: Find package IDs at winstall.app. Search by app name and copy the exact ID — for example, Google.Chrome or Adobe.Acrobat.Reader.64-bit.
Finding Package IDs
Winget package IDs follow a Publisher.AppName format. A few common examples:
Google.ChromeMozilla.FirefoxAdobe.Acrobat.Reader.64-bitMicrosoft.VisualStudioCode7zip.7zip
Use winstall.app or run winget search <app name> from a terminal to find the correct ID before configuring the action.
⚠️ WARNING: Winget IDs are case-sensitive and must be exact. A typo will cause the action to fail at run time.
Conditions
Restrict when this action runs based on device attributes or the outcome of a previous action. Expand the Conditions section to add conditions.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for settings including action name, failure behavior, output variables, and retries.
See Actions Overview for the full reference on additional options available on every action.
FAQ
What happens if the package is already installed? Winget will skip the install or report that the package is already present. The action completes without error in most cases, but behavior can vary by package.
Do I need to add an Install Winget step first? No. If Level's winget isn't on the device yet, this action installs it automatically before running.
Can I install multiple apps in one action step? Yes. Add as many package IDs as you need, each separated by
Tabor a comma. They'll all install in the same step.What if a package ID doesn't exist? The action will fail for that package. Check the ID against winstall.app or
winget searchto confirm it's valid before saving.Who can configure this action? Any technician with permission to create or edit automations in the relevant group.