> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/app-builder/build/data-flow.md).
# Data Flow
Visualize app components, data stores, and connections across your architecture.
Data Flow is an architecture diagram of how an app works — its pages, services, integrations, external systems, and data stores, and the connections between them. Qore generates it from the app as you build. Open it from the app workspace's **More** menu → **Data Flow**.
The Data Flow diagram.
## What it shows
Each component in the diagram is typed — a **Page**, a **Backend** service, an **Integration**, an **External** system, a **Database**, or the **User** — and each connection is labelled with what it does. For example, an authentication flow might run from the user, to a login page, to a Google OAuth integration, out to Google's identity service, back to a backend auth service, and into a Postgres database, with each arrow labelled ("redirects to Google", "callback to backend", "saves/updates user", and so on).
An **Overview** panel summarizes the app in plain language — what it does and what it's built with. Select any component or connection to see what that part does.
{% hint style="info" %}
The diagram is generated from the app and reflects the selected build version, so it updates as the app changes. It's a map for understanding the app, not an editor — you change the architecture by changing the app in the build conversation.
{% endhint %}
## Why this matters
* Data Flow is the fastest way to understand, explain, or review how an app is put together.
* It stays in sync with the app because Qore regenerates it as the app changes.
## Related
{% content-ref url="/pages/6CB3ux2H16RPihpNE3qg" %}
[Integrations Hub](/ai-workbench-qore/console/integrations-hub.md)
{% endcontent-ref %}
{% content-ref url="/pages/bc7662d99efc00ab94438c3b32248b84a7af247f" %}
[App Workspace](/ai-workbench-qore/console/app-builder/app-workspace.md)
{% endcontent-ref %}
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul AI-assisted, human-approved
{% endcolumn %}
{% endcolumns %}
---
# 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.uptiq.ai/ai-workbench-qore/console/app-builder/build/data-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.
