> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/kaiya-apps/how-to-create-a-kaiya-app/connect-data-while-building-an-app.md).

# Connect data while building an App

Connect a new data source from the App conversation, so Kaiya can build a Business View and an App on it, and choose whether the App's data is live.

If the data you need isn't connected to Tellius yet, you can connect it without leaving the conversation. Kaiya then builds and checks a Business View on the new data, and builds the App on that Business View.

1. In the message box, select **Connect data**. The **Business View workspace** opens beside the conversation, on the **Data Sources** tab.
2. Under **Connect a Datasource**, select your source, for example **Snowflake**, **Redshift**, **BigQuery** or **Databricks Delta Lake**.
3. Fill in the connection details. For Snowflake, choose an **Authentication Type** (**Direct**, **Key Pair** or **OAuth**), then enter the **Host**, **User**, **Password** and **Role**, and a **Datasource Name**.
4. Select **Save and Browse Host** to save the connection and browse the data it holds.

To use a connection that already exists, scroll to the bottom of the panel and pick it from **Select existing datasource**. If your source isn't in the list, select **Connect via the main page**. See [Create new datasource](https://help.tellius.com/data/create-new-datasource).

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FTDnIMEv9VDogtGDCP6RW%2Fab-connect-data.png?alt=media&amp;token=112a7b1e-cd53-4614-8b11-cb571a8acd9d" alt="The Connect data button in the message box and the Business View workspace with the list of data sources" width="563"><figcaption></figcaption></figure>

Kaiya asks whether the App's data should be live. A live App queries your data each time someone views it. An App that isn't live shows the results of its last refresh. Kaiya also knows when a live App isn't the right choice, and says so rather than building one that doesn't suit your data. See [Live data in Apps](https://help.tellius.com/kaiya/kaiya-apps/live-data-in-apps).

{% hint style="info" %}
**Live or not live?** Choose live when readers will filter the App by values such as region, brand or date and need current numbers each time. Live cells can't drill down or change what they group by. Sections built from calculation steps always show data from the last refresh, even in a live App.
{% endhint %}

When the data is connected, continue with [Step 3: Review the plan and let Kaiya build](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app#step-3-review-the-plan-and-let-kaiya-build).


---

# 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://help.tellius.com/tellius-6.4/kaiya/kaiya-apps/how-to-create-a-kaiya-app/connect-data-while-building-an-app.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.
