> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/classic-tutorials/creating-a-customer-portal/prepare-your-data.md).

# Prepare your Data

In this section you will learn how to prepare your data for creating a customer portal

You can build Portals with data from pretty much **Any Data Source**: `Firebase, Sheets`, `Airtable`, `Stripe`, `REST API`, and so on. We'll use **Airtable** in our example.

In our case, we will use two tables: Projects and Tasks. **The projects** table has the `Link to Tasks` column and the **Tasks** have the `Project` column in it.

**Projects Table:**

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MizDMaSiLvRScLSbyrU%2F-Mj-Bg-HPEyaeOMcP1V0%2Fimage.png?alt=media\&token=e63b633e-6aed-452e-a88e-759465429c05)

**Tasks Table:**

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MizDMaSiLvRScLSbyrU%2F-Mj-BmpQEDNYIpgdLvxU%2Fimage.png?alt=media\&token=b22ea952-26d5-40e2-b7a4-ce70c97242a8)

Next, we **generate the app**:

{% content-ref url="/pages/-Mizqw2Kj8Hu3vyq-0ba" %}
[Generate the App](/classic-app-builder/classic-tutorials/creating-a-customer-portal/generate-the-ui.md)
{% endcontent-ref %}


---

# 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.jetadmin.io/classic-app-builder/classic-tutorials/creating-a-customer-portal/prepare-your-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.