> 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/element/upload-a-file.md). # Upload a File This is a pre-built Action located under the captured element. The functionality of this Action in Avo Assure is to upload a file from the specified system location based on the input provided. The result is stored in the given dynamic variable for further use during test execution ## Syntax **Input Value**: `;;` | Argument | Description | | ----------------------------------------- | ------------------------------------------------------------------------- | |

\
(Required)

| Provide the path or location of the specific file from the local system. | |

\
(Required)

| Provide the name of the particular file you want to upload. | |

\
(Required)

| Provide the wait time (in seconds) you want before performing the action. | {% hint style="info" %} **Note:** The action will be executed after the specified wait time, if provided. {% endhint %} **Output Value**: `(Optional);(Optional)` | Argument | Description | | ----------------------------------------------------------- | ----------------------------------------------------------------- | | \(Optional);\(Optional) | This dynamic variable stores the status as **True** or **False**. | ### Example: Uploading a File to the Application In this example, we explain how to upload a file to the application from a specified path with the given file name, after waiting for the defined duration. * **Action**: Upload a File * **Input Value**: C:\Users\Downloads;Sample;2 * The first argument (**C:\Users\Downloads**) specifies the folder path where the file is located. * The second argument (**Sample**) specifies the name of the file to be uploaded. * The third argument (**2**) specifies the number of seconds to wait before performing the upload. * **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 a File** action reads the details from the **Input Value** column (**C:\Users\Downloads;Sample;2**). It locates the file in the specified folder, waits for the defined duration, and uploads the file to the application. The outcome of the upload operation (**True**) is stored in the **{Status}** variable.
--- # 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.avoautomation.com/avo-assure/actions/web/element/upload-a-file.md?ask=&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.