> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/data-and-assets/connections/databricks.md).

# Databricks

Connect to Databricks with an access token.

## Connection details

| Field               | What to enter                                                                                                                       |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Server hostname** | Your workspace's server hostname, such as `adb-1234567890123456.7.azuredatabricks.net`. You can include `https://` or leave it out. |
| **HTTP path**       | The HTTP path of the SQL warehouse or cluster to use                                                                                |
| **Access token**    | A Databricks personal access token or service principal token                                                                       |

You'll find the server hostname and HTTP path in your SQL warehouse's or cluster's connection details in Databricks. The access token is never shown again after you save it.

## Working with Spark

For Spark workloads, use the **Spark Connect** environment preset, which includes the Databricks SQL connector and the PySpark client. See [Environment presets](/zerve-docs/environments/environment-presets.md).

See [Data connections](/zerve-docs/data-and-assets/connections.md) for creating, naming and attaching connections.


---

# 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.zerve.ai/zerve-docs/data-and-assets/connections/databricks.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.