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

# Databricks Setup

Connect a Databricks SQL warehouse to Zenlytic and verify access to your catalogs and tables.

To connect Zenlytic to Databricks, you'll need to configure the connection using a personal access token. Here's how to do it:

## Step 1: Create a Personal Access Token

1. Log into your Databricks workspace
2. Go to User Settings (click your username in the top right)
3. Click on "Developer" tab
4. Click "Generate New Token"
5. Give it a name (e.g., "Zenlytic Integration")
6. Set an expiration date
7. Click "Generate"
8. Copy the token (you won't be able to see it again)

![Databricks Setup 1](https://1577702444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT9EV2yuH6oO9jfgfgYUW%2Fuploads%2Fgit-blob-a96ee8ec03ab5a69cf6c47372d5017596c0957cf%2Fdatabricks-setup-1.png?alt=media)

## Step 2: Get Your Workspace URL

1. In your Databricks workspace, look at the URL in your browser
2. It should look like: `https://your-workspace.cloud.databricks.com`
3. Copy this URL

![Databricks Setup 1](https://1577702444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT9EV2yuH6oO9jfgfgYUW%2Fuploads%2Fgit-blob-a96ee8ec03ab5a69cf6c47372d5017596c0957cf%2Fdatabricks-setup-1.png?alt=media)

## Step 3: Add the Connection in Zenlytic

1. In Zenlytic, go to Settings > Data Sources
2. Click "Add Data Source"
3. Select "Databricks" from the list
4. Enter the connection details:
   * **Workspace URL**: Your Databricks workspace URL
   * **Personal Access Token**: The token you generated
   * **HTTP Path**: Usually `/sql/1.0/warehouses/<warehouse-id>`

![Databricks Setup 2](https://1577702444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT9EV2yuH6oO9jfgfgYUW%2Fuploads%2Fgit-blob-1e9615e2d145ead434e609097f61987842a02735%2Fdatabricks-setup-2.png?alt=media)

## Step 4: Configure HTTP Path

To find your HTTP path:

1. Go to SQL Warehouses in Databricks
2. Click on your warehouse
3. Look for the "Connection Details" section
4. Copy the HTTP Path

![Databricks Setup 3](https://1577702444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT9EV2yuH6oO9jfgfgYUW%2Fuploads%2Fgit-blob-d2b06797963d4625b970cb0098d62735e55538e6%2Fdatabricks-setup-3.png?alt=media)

## IP Whitelisting

If you use IP whitelisting in your data warehouse, whitelist the following IP addresses:

```
184.73.175.163 
18.209.132.30
```

## Step 5: Test Your Connection

1. Click "Test Connection" to verify it works
2. If successful, click "Save"
3. You should now be able to see your Databricks tables in Zenlytic


---

# 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.zenlytic.com/data-sources/databricks_setup.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.