> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/file-and-folder/folder-exists.md).
# Folder exists
Folder exists is an action used to check whether a folder exists on the computer's hard drive at the specified path. The return result of this action is a Logic value: True (if the folder is found) or False (if the folder does not exist).
This action is often used as a precursor before performing operations such as creating a new folder, deleting a folder, or moving files into it, helping the script run smoothly and not abruptly stop due to path errors.
🎥 Watch the tutorial video: [Here](https://youtu.be/EH7olDLAb9c).
#### Configuration parameters:
* Folder Path: The absolute path to the folder to check on the computer (e.g., `D:\GPM_Data`).
* Output variable: The name of the variable to store the check result (`True` or `False`).
#### Practical example: Check the Profile image storage folder before downloading
Suppose you have an automated script that downloads a profile picture from the internet to save in a separate folder for each Profile structured as: `D:\GPM_Data\Profile_1`. If the `Profile_1` folder has not been created on drive D, the subsequent image download action will fail immediately.
To handle this logic intelligently, you configure as follows:
* Step 1: Call the Folder exists action, fill in the folder path to check as `D:\GPM_Data\Profile_1`, and name the output variable `$isFolderReady`.
* Step 2: Use an If condition block to check: `If $isFolderReady = False` (meaning this folder does not exist).
* Step 3: Inside the If block, call the Create folder action with the path `D:\GPM_Data\Profile_1` to have the system automatically create this folder.
Result: The script will automatically check first. If the folder does not exist, it will create it before proceeding to download the image, ensuring the flow runs safely and never crashes.
---
# 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.gpmautomate.com/automate-en/action-guide/file-and-folder/folder-exists.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.
