Set Up Databricks in Kizen

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

Audience: Admins, Developers, Solution Architects

Purpose: Explains how to configure the Databricks integration to use live Databricks data in Agentic Workflows

Overview

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.

Set up Databricks in Kizen to read and write live Databricks data in Agentic Workflows.

---

Before You Begin

To set up Databricks in Kizen, 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 Kizen.

Note: If you don't have the necessary PAT, you can generate one from the developer settings in Databricks. See the Databricks documentation for details.

---

Set Up Databricks in Kizen

To set up Databricks in Kizen:

1

Go to the App Marketplace

In Kizen, go to the global navigation, and select Platform > App Marketplace.

2

Turn on the Databricks integration

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

3

Configure the integration secret

On the Databricks Connection card, select Manage Secrets to open the Secret Manager in Kizen. Then find the integration secret for the Databricks connection, open its Actions menu, and select Edit. The Update Integration Secret modal appears.

4

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:

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

Store multiple environments as nested JSON objects:

{
  "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.

Note: ​Kizen 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 Kizen so you can refer to the full set whenever you add a new environment.

5

Save the integration secret

Select Save.

---

What's Next

Continue to Add Databricks Data to an Agentic Workflow to read or write data to your Databricks SQL Warehouse from an Agentic Workflow in Kizen.

Related Topics

• Databricks
• Add Databricks Data to an Agentic Workflow
• Troubleshoot Databricks

---

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.