> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-apps/integrations/databricks/set-up-databricks-in-kizen.md).

# Set Up Databricks in Kizen

Learn how to configure the Databricks integration in Kizen to use live Databricks data in Agentic Workflows.

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Explains how to configure the Databricks integration to use live Databricks data in <code class="expression">space.vars.automations</code>
{% endhint %}

## Overview

{% hint style="warning" %}
**Caution:** This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

Set up Databricks in <code class="expression">space.vars.Kizen\_company\_name</code> to read and write live Databricks data in <code class="expression">space.vars.automations</code>.

***

## Before You Begin

To set up Databricks in <code class="expression">space.vars.Kizen\_company\_name</code>, you need:

* Any Databricks workspace with Unity Catalog enabled and a working SQL Warehouse. You don't need a specific plan tier beyond these requirements.
* A Databricks Personal Access Token (PAT) with the `Can Use` permission on the desired Databricks SQL Warehouse and `SELECT` and `MODIFY` grants on the target Unity Catalog, schema, and table.
* Org Admin access in <code class="expression">space.vars.Kizen\_company\_name</code>.

{% hint style="info" %}
**Note:** If you don't have the necessary PAT, you can generate one from the developer settings in Databricks. See the [Databricks documentation](https://docs.databricks.com/aws/en/dev-tools/auth/pat) for details.
{% endhint %}

***

## Set Up Databricks in Kizen

To set up Databricks in <code class="expression">space.vars.Kizen\_company\_name</code>:

{% stepper %}
{% step %}

#### Go to the App Marketplace

In <code class="expression">space.vars.Kizen\_company\_name</code>, go to the global navigation, and select **Platform** > **App Marketplace**.

<div data-with-frame="true"><figure><img src="https://3898351136-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQd8ufpN7wkdnx7JtgoeZ%2Fuploads%2Ffzoos6vbr0prt7BbpKCy%2Fglobal_platformappmarketplace.png?alt=media&amp;token=98eabc11-f0ba-4a44-8bc2-e863201d234e" alt="The App Marketplace menu item under the Platform group in the global navigation" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Turn on the Databricks integration

Find the Databricks Connection card, and turn on the integration.

<div data-with-frame="true"><figure><img src="https://3898351136-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQd8ufpN7wkdnx7JtgoeZ%2Fuploads%2FUfuEZCF2D6VhvLBJ9ZMu%2Fdatabricks_appon.png?alt=media&amp;token=5022e41b-89c8-42e0-b959-16ea7c97c6eb" alt="The Databricks Connection card" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Configure the integration secret

On the Databricks Connection card, select **Manage Secrets** to open the Secret Manager in <code class="expression">space.vars.Kizen\_company\_name</code>. Then find the integration secret for the Databricks connection, open its Actions menu, and select **Edit**. The Update Integration Secret modal appears.

<div data-with-frame="true"><figure><img src="https://3898351136-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQd8ufpN7wkdnx7JtgoeZ%2Fuploads%2Fl4hciAKqFooOhelhplnq%2Fdatabricks_updateintegrationsecret.png?alt=media&amp;token=033905ce-006d-495d-909f-358de22aa98b" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Enter your Databricks connection credentials

In the Integration Secret field of the modal, enter your Databricks connection credentials as a JSON object. The JSON object must contain `host`, `warehouse_id`, and `token` keys, like this:

```json
{
  "host": "workspace_host",
  "warehouse_id": "warehouse_id",
  "token": "personal_access_token"
}
```

Store multiple environments as nested JSON objects:

```json
{
  "production_db": {
    "host": "workspace_host",
    "warehouse_id": "warehouse_id",
    "token": "personal_access_token"
  },
  "staging_db": {
    "host": "workspace_host",
    "warehouse_id": "warehouse_id",
    "token": "personal_access_token"
  }
}
```

For descriptions of the keys, see the following table:

| Key            | Type     | Description                                                                                                                              |
| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `host`         | `String` | The server host name of the target data warehouse. Don't include the `https://`.                                                         |
| `warehouse_id` | `String` | The ID of the target data warehouse. Find this value in the last segment of the target data warehouse's HTTP path, after `/warehouses/`. |
| `token`        | `String` | Your Databricks developer access token. If you don't have one, generate one for the SQL scope.                                           |

Get the values for `host` and `warehouse_id` in the connection details of the SQL warehouse in Databricks. You can also create the PAT from this page. For more information, see the [Databricks documentation](https://docs.databricks.com/aws/en/integrations/compute-details).

{% hint style="info" %}
**Note:** ​<code class="expression">space.vars.Kizen\_company\_name</code> hides your secret once you submit it, so you can't append a new environment to an existing secret. You must re-enter the credentials for all your environments along with the new one. Consider keeping a secure record of each environment's connection details outside of <code class="expression">space.vars.Kizen\_company\_name</code> so you can refer to the full set whenever you add a new environment.
{% endhint %}
{% endstep %}

{% step %}

#### Save the integration secret

Select **Save**.
{% endstep %}
{% endstepper %}

***

## What's Next

Continue to [Add Databricks Data to an Agentic Workflow](/docs/integrations-and-apps/integrations/databricks/add-databricks-data-to-an-agentic-workflow.md) to read or write data to your Databricks SQL Warehouse from an <code class="expression">space.vars.automation</code> in <code class="expression">space.vars.Kizen\_company\_name</code>.

<details>

<summary><strong>Related Topics</strong></summary>

* [Databricks](/docs/integrations-and-apps/integrations/databricks.md)
* [Add Databricks Data to an Agentic Workflow](/docs/integrations-and-apps/integrations/databricks/add-databricks-data-to-an-agentic-workflow.md)
* [Troubleshoot Databricks](/docs/integrations-and-apps/integrations/databricks/troubleshoot-databricks.md)

</details>

***

*Databricks and Unity Catalog are trademarks of Databricks, Inc. Delta Lake is a trademark of the Delta Lake project and its contributors. Kizen's Databricks integration is not affiliated with, sponsored by, or endorsed by Databricks, Inc. or the Delta Lake project.*


---

# 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://developer.kizen.com/docs/integrations-and-apps/integrations/databricks/set-up-databricks-in-kizen.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.