> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-artifacts/get-artifactory-path.md).

# Get Artifactory Path

Get the Artifactory Path you need to configure a step in a JFrog Connect workflow.

This page describes how you get the Artifactory Path that you need to configure an update flow step in JFrog Connect. 

The procedure is applicable to the following step types: 

* [**Download Artifact**](/features-new-ui/deployments/update-flow/step-types/download-artifacts.md): Can be an artifact of any file type.
* [**Update Image**](/features-new-ui/deployments/update-flow/step-types/update-image.md): Must be a file of type \<image>.swu.
* [**Deploy Docker Compose**](/features-new-ui/deployments/update-flow/step-types/use-docker-compose.md): The file in the Artifactory Path must be of type \<docker compose>.yaml.
* [**Download Release Bundle**](/features-new-ui/deployments/update-flow/step-types/download-release-bundle.md): For Release Bundle Path.&#x20;

To get the Artifactory path, do the following:

1. In the left navigation pane of JFrog Connect, choose **JFrog Platform**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/W8Oe8h6gbmV5f7jT7rzM/get-artifactory-path-01.png" alt="" width="215"><figcaption></figcaption></figure></div>

2. In the left navigation pane of JFrog Platform, choose **Artifactory** and **Artifacts**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/X819EkOfVUTRPsJePAAh/get-artifactory-path-01-1.png" alt="" width="218"><figcaption></figcaption></figure></div>

3. In Artifactory, select the artifact you want to download. If you need help finding your artifact, see [Browsing Artifacts](https://jfrog.com/help/r/jfrog-artifactory-documentation/browsing-artifacts) in the Artifactory documentation.
4. In the General Info, copy the **Repository Path** to the clipboard.<br>

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/ZJMWevfKgmqAXA0XSO7z/get-artifactory-path-02.png" alt=""><figcaption></figcaption></figure></div>

5. Go to your Download Artifact action configuration in Connect (or any action where you need an Artifactory Path). Paste the Repository Path (already on the clipboard) into the **Artifactory Path** field.

Now you can complete the rest of your step configuration in Connect and save it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-artifacts/get-artifactory-path.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.