> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/image/upload-file-to-application.md).

# Upload File to Application

This is a pre-built Action located under the captured image element. The functionality of this action in Avo Assure is to upload a file from the specified local system path to the application. The result is stored in the given dynamic variable for further use during test execution

## **Syntax**

**Input Value**: `<File path>;<File name>;<Wait (in seconds)>`

| Argument                                  | Description                                                                        |
| ----------------------------------------- | ---------------------------------------------------------------------------------- |
| <p>\<File path><br>(Required)</p>         | Provide the path or location of the file you want to access from the local system. |
| <p>\<File name><br>(Required)</p>         | Provide the name of the specific file you want to upload.                          |
| <p>\<Wait (in seconds)><br>(Optional)</p> | Provide the time in seconds you want to wait before the action is performed.       |

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>Optional)`

| Argument                                                   | Description                                                       |
| ---------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>Optional) | Both dynamic variable stores the status as **True** or **False**. |

**Example: Uploading a File to the Target Application Window**

In this example, we explain how to perform a file upload operation in the target application window by providing the required file path, file name, and wait time.

* **Action**: Upload File to Application
* **Input Value**: C:\Documents;report.pdf;5
  * The first argument (**C:\Documents**) specifies the folder path where the file is located.
  * The second argument (**report.pdf**) specifies the name of the file to be uploaded.
  * The third argument (**5**) specifies the wait time (in seconds) allowed for the upload operation to complete.
* **Output Value**: {Status}
  * The result of the upload operation is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the file is uploaded successfully.
    * **False**: If the file is not uploaded successfully.
* **Logical Explanation**: The **Upload File to Application** action reads the folder path, file name, and wait time from the **Input Value** column (e.g., **C:\Documents;report.pdf;5**). The action locates the specified file in the provided folder path and attempts to upload it to the target application during execution. The wait time determines how long the action should wait for the upload process to complete. The result of the upload operation (**True**) is stored in the **{Status}** variable.

<figure><img src="/files/lL1fwpp4OQI5JRC2lXPM" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/image/upload-file-to-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.