# Download Artifact

The Download Artifact step type enables you to create a flow that pulls artifacts from your Artifactory instance and deploys them to your edge devices. You can one or multiple artifact actions in an update flow.

Deployments using Artifactory consider the checksums of the files delivered. Therefore, the devices will pull only the diffs when downloading updates to files.

## Prerequisites

* JFrog Connect and JFrog Platform accounts.
* Connect Agent 6.0 or later and at least one device registered.
* One or more files ready for deployment and stored in your Artifactory repository.
* In the [Create Update Flow](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow) procedure, completed through Step 3.

### Add a Step and Configure the Step Type <a href="#add-a-step-and-configure-the-step-type" id="add-a-step-and-configure-the-step-type"></a>

To add a step and configure the step type you have chosen, do the following:

1. In the Create New Flow page, click **Add Step**.
2. In the **Step Type** dropdown list, choose **Download Artifact**, give the step a **Step** **Name**, and create the step. You can change the step name afterwards if you need to.
3. **JFrog Registry:** Choose the JFrog Registry where your artifact is stored. If the registry does not appear in the list, go to [Add JFrog Registry](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-jfrog-registry) to add yours to the list. Then return to this configuration and the added registry will appear in the list.

{% hint style="success" %}
**Tip**: If you want the step to pull content from an Artifactory Edge account, complete the procedure in [Add JFrog Registry](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-jfrog-registry), and then choose that registry as your JFrog Registry.
{% endhint %}

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FN1lZm278OG6Cd3OIUkHO%2Fdownload-artifact-nui-01.png?alt=media&#x26;token=d39759a4-9922-4223-9f35-f5c0e1dc0449" alt="" width="563"><figcaption></figcaption></figure></div>

4. **Artifactory Path**: Enter the path of your artifact (i.e., the Artifactory Repository Path in your Artifactory repository). The path usually has a structure like the following: `repository-name/artifact/version/file.txt`. You can also make all or part of the path a parameter. For example, you could make the version folder a parameter: `generic-repo/artifact/{{version}}/file.text`. Then you enter the version value when the actual deployment is run.
5. **Device Path**: Enter the destination path on the device. The directory on the device must exist beforehand or the update will fail. Connect does not automatically create directories when deploying updates. You may create a folder using the Run Command step type.

{% hint style="success" %}
**Tip**: If you need help finding the Artifactory Path in Artifactory, see [Get Artifactory Path.](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-artifacts/get-artifactory-path)
{% endhint %}

6. If you want to deliver more than one artifact, add a new step for each artifact.
7. Configure your [On Failure](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/on-failure-and-rollback) policy and instructions for rolling back.&#x20;
8. Save your step configuration.

## What’s Next?

Learn how to build a workflow using a [Download Release Bundle](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-release-bundle).