> 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-guides/file-and-folder/file-exists.md).

# File exists

This action helps the tool check whether a file already exists on the computer. The result returned is very simple: True (if the file is found) or False (if not found).

* Purpose: Used in conjunction with the `If` block for smarter handling, avoiding situations where the tool encounters errors or crashes unexpectedly when you ask it to open a file that does not actually exist.

#### Configuration parameters:

* File Path: The absolute path to the file to be checked on the computer (e.g., `D:\data\accounts.txt`).
* Output variable: The name of the variable that stores the check result (`True` or `False`).

#### Real-world example: Checking the configuration file before running the script

Suppose you write a script that automatically fills in information and requires the script to read data from the file `D:\GPM\config.json`. If the user forgets to create this file or enters the wrong path, the script will encounter a system error when it reaches the file reading command.

To handle this safely, you configure the script as follows:

* Step 1: Call the File exists action, enter the path `D:\GPM\config.json`, and name the output variable `$isFileReady`.
* Step 2: Use the If block to check: `If $isFileReady = False`.
* Step 3: Inside this If block, you call the Throw action with the content: `"Error: You have not created the config.json file on drive D, please check again!"`.

Result: The script will automatically check first. If the file does not exist, it will proactively stop the flow and trigger a visual red warning to let you know, instead of trying to continue and then crashing the script.

<figure><img src="/files/ZuoR0kwb8SyZsrhiNv35" 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.gpmautomate.com/automate-en/action-guides/file-and-folder/file-exists.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.