> 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/desktop/email/switch-to-folder.md). # Switch to folder This is a pre-built action in Avo Assure and comes under **@Email Element.** The functionality of this action in Avo Assure is to switch between various folder in the outlook desktop application based on its application path of the folder provided in the input value field. ### Syntax **Input Value:**`` | Argument | Description | | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | |

(Required)

Specify the Outlook folder path and followed by a ‘\’ and the folder name
(Example: \\\Inbox )

| {% hint style="warning" %} **Note:** We need to right-click on the folder in the outlook desktop application that the user wants to switch, copy the path, and add it in the input followed by a ‘\’ and the folder name, as shown in the example below. Example: \\\\\Inbox\* {% endhint %} **Output Value:**

Argument	Description
N/A	Not Applicable

**Example** **Switches the focus to the specified Outlook folder in the desktop application** The **Switch to folder** action takes the value from the **Input Value** column (e.g., **\\\\\Inbox**) and switches the current view in the Outlook desktop application to the specified folder path.

--- # 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/desktop/email/switch-to-folder.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.