> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/data.md).

# Data

Every Zingy app comes with it's own database for storing data. This database can store various types of data, such as text, numbers, files, etc.

The App Database can be managed through the Data tab as shown below:

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2F93uAjjLodVdPGobwJRts%2Fimage.png?alt=media&amp;token=06d0ea2f-c7d4-4e93-b5b0-07f307b1ae5f" alt=""><figcaption><p>Zingy App Editor - Data tab</p></figcaption></figure>

Using the data tab you can:

* [Create Database Tables](/app-editor/data/database-tables.md#creating-a-database-table)
* [Modify Database Tables](/app-editor/data/database-tables.md#modifying-a-table)
* [Delete Database Tables](/app-editor/data/database-tables.md#deleting-a-table)
* Configure [Access (Security) rules](/app-editor/data/database-tables.md#access-security-rules) for Database Tables
* [Manage Database Queries](/app-editor/data/database-queries.md)
* Launch the [Data Tool](/app-editor/data/data-tool.md)

***

## Overview

The following video shows a general overview about Zingy's database features and the ways in which your app can read, modify and show data.&#x20;

{% embed url="<https://youtu.be/3h_bRxORBlY>" %}
Video: Database Features
{% endembed %}

## Page Flow blocks

The following is a list of some important [Page Flow ](/app-editor/page-flow.md)blocks related to your app's database. For a complete listing of all Page Flow blocks, please see [Toolbox Blocks](/app-editor/page-flow/toolbox-blocks.md).

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;">Data Read</mark></td><td><a href="/app-editor/page-flow/toolbox-blocks/data-read.md">Data Read</a></td></tr><tr><td><mark style="color:blue;">Data Record Loop</mark></td><td><a href="/app-editor/page-flow/toolbox-blocks/data-record-loop.md">Data Record Loop</a></td></tr><tr><td><mark style="color:blue;">Data Add Record</mark></td><td><a href="/app-editor/page-flow/toolbox-blocks/data-add-record.md">Data Add Record</a></td></tr><tr><td><mark style="color:blue;">Data Update Record with ID</mark></td><td><a href="/app-editor/page-flow/toolbox-blocks/data-update-record-with-id.md">Data Update Record with ID</a></td></tr><tr><td><mark style="color:blue;">Data Delete Record with ID</mark></td><td><a href="/app-editor/page-flow/toolbox-blocks/data-delete-record-with-id.md">Data Delete Record with ID</a></td></tr></tbody></table>

## See Also

<table data-view="cards"><thead><tr><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/app-editor/data/database-tables.md">Database Tables</a></td></tr><tr><td><a href="/app-editor/data/database-queries.md">Database Queries</a></td></tr><tr><td><a href="/app-editor/data/data-tool.md">Data Tool</a></td></tr></tbody></table>


---

# 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.zingy.ai/app-editor/data.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.