Introduction
Download a file from Level's built-in file repository to a managed device during an automation run. Level checks the file against the device's existing copy before downloading — if the file is already present and unchanged, the download is skipped.
For downloading files from an external URL instead, see the Download File via URL action.
Download File Action
From the automation pipeline in edit mode, click + and select Download file from the Files category.
The action panel opens with three configuration fields.
Repository file
Select the file to download from a dropdown list of all files in your Level file repository.
Destination path
The directory on the device where the file should be saved. Required.
Example: C:\path\to\file
Click (x) to insert a variable, system variable, or custom field reference. The value resolves at runtime.
File name
The name to give the file on the device. Required.
Example: setup.exe, config.json
Click (x) to insert a variable, system variable, or custom field reference.
Checksum Verification
This action is checksum-aware in two ways:
Before download: Level compares the repository file's checksum against any existing file at the destination path. If the file is already present and matches, the download is skipped.
After download: Level verifies the downloaded file's checksum against the repository copy to confirm the transfer completed without corruption.
This makes the action safe to run repeatedly — devices that already have the current version of the file are unaffected.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on additional options available on every action.
FAQ
Where do I upload files to the repository? From Automations → Files in the Level web interface. Files uploaded there become available in the Repository file dropdown for this action.
What happens if the destination path doesn't exist on the device? Level creates the path automatically.
What if the download fails mid-transfer? The post-download checksum verification will fail, and the action will be marked as failed. Your On action failure setting in Additional options controls whether the pipeline stops or continues.
Who can add or modify Download File actions? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.