> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-management/workbench/model-data/flow-models/create-a-flow.md).
# Create a Flow
In order to create a Flow, you can either start from scratch or create a Flow from an existing dataset.
To create a Flow, go to D**ata** in the **View Selector** and click on the **+ button** next to **Models.** This should open a panel asking which kind of model you want to create, then click on **Flow.**
You can also click on **New** > **Model** > **Flow.**
You can then give your flow a name, and select if you want to start from scratch or from an existing dataset.
If you choose to start from an existing dataset the flow created will contain the[ primary keys ](/data-management/workbench/understanding-datasets/primary-keys.md)and the [relationships](/data-management/workbench/understanding-datasets/relationships.md) of the base dataset.
---
# 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.whaly.io/data-management/workbench/model-data/flow-models/create-a-flow.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.
