> 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/create-folder.md).

# Create folder

Create folder is an action used to initialize a completely new folder on the computer's hard drive at the specified path.

This action has an intelligent and safe operating mechanism:

* If the folder does not exist: The system will automatically create the new folder (including creating parent folders if they are not already available).
* If the folder already exists: The system will skip and proceed to the next action, absolutely not overwriting or affecting the data inside the old folder.

🎥 Watch the tutorial video: [Here](https://youtu.be/EH7olDLAb9c).

#### Configuration parameters:

* Folder Path: The absolute path to the folder you want to initialize (e.g., `D:\GPM_Softwares\Data_Crawler`).

#### Practical example: Automatically create a folder to save screenshots by date

When running account farming scripts or scraping data, you often need to take screenshots of the browser when encountering errors for easy review. To manage easily, you want the system to automatically group images into a separate folder each day in the date format (e.g., `D:\GPM_Screenshots\2026-06-29`).

* Configuration method:
  * Before calling the screenshot command, you call the Create folder action.
  * Folder Path: You combine a fixed path with the system time variable, filling in the box: `D:\GPM_Screenshots\$currentDate`.
* Result: When the script runs this step, the system will automatically check if there is already a folder named with the current date (e.g., `2026-06-29`). If not, it will automatically create a new clean folder. The subsequent Screenshot actions just need to point the save path to this folder, keeping your data neatly categorized by day.

<figure><img src="https://2961903581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpIRrmOLZkhHBXdAiidIw%2Fuploads%2Fgit-blob-5f71e08cf4c8a6b567f84a83dcee1736d9c2507d%2Fff-14.png?alt=media" 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 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/create-folder.md?ask=<question>&goal=<user_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.
