Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.replit.com/llms.txt

Use this file to discover all available pages before exploring further.

The Databricks connector is available exclusively on the Enterprise plan.
Replit home prompt box with the Templates dropdown open, showing the Databricks App org template
The Databricks connector lets Replit Agent query your Databricks workspace. Builders can create dashboards, reporting tools, and data applications using natural language. No SQL expertise required. Setup is a one-time process that involves a Databricks admin and a Replit organization admin. Once configured, builders with access can use the connector from Replit. This guide covers the full setup across three roles:
  1. Databricks admin: creates the service principal and grants permissions in Databricks.
  2. Replit admin: configures the connector in Replit.
  3. Builder: starts building with Databricks data.

​
Prerequisites

Before you start, confirm the following. Roles

​
Step 1: Create a service principal in Databricks

You must be a Databricks account admin or workspace admin to complete this step.
The Databricks admin creates a machine-to-machine identity, called a service principal, that Replit uses to connect to Databricks.
1

Open Settings

In Databricks, select your avatar in the top-right corner, then select Settings.
Databricks workspace menu with Settings selected
2

Select Identity and access

In the Settings sidebar, select Identity and access.
Databricks Settings page with Identity and access in the sidebar
3

Manage service principals

Under Management and permissions, find Service principals and select Manage.
Identity and access settings page showing the Service principals Manage button
4

Add a new service principal

Select Add service principal, then select Add new.
Add service principal dialog with the Add new button
5

Name the service principal

Enter a clear name for the service principal, then select Add.
Add service principal dialog with a service principal name entered
6

Confirm the service principal details

After Databricks creates the service principal, confirm it is active. Keep this page open if you need the service principal details while configuring the Replit connector.
Databricks service principal details page
7

Grant access

Open the Permissions tab, select Grant access, choose the service principal, set the permission to Manage, then select Save.
Grant access dialog for a Databricks service principal with Manage permission selected

​
Step 2: Get your SQL Warehouse connection details

The Replit connector needs Databricks SQL Warehouse connection details to route queries to the right compute resource.
1

Open SQL Warehouses

In the Databricks sidebar, select SQL Warehouses.
Databricks SQL Warehouses page showing available warehouses
2

Select or create a warehouse

Select the SQL Warehouse you want Replit Agent to use. If you do not already have one, select Create SQL warehouse and create a new warehouse.
3

Copy connection details

Open the warehouse and select Connection details. Locate the Server hostname and HTTP path values. You need these values when creating the Databricks connector in Replit.
Databricks SQL Warehouse connection details page with server hostname and HTTP path

​
Step 3: Create the Databricks connector in Replit

You must be a Replit organization admin to configure connectors.
The Replit admin adds the Databricks connection details to Replit so builders can use the connector.
1

Navigate to Integrations

From your organization home, open the Integrations page. Under Connectors, find Databricks (Service Principal) and select Sign in.
Replit Integrations page filtered to Databricks, showing the Databricks (Service Principal) connector with a Sign in button
2

Confirm the connection

Replit shows a confirmation dialog before redirecting to Databricks for authentication. Review the details and select Continue to Databricks.
Connect Databricks dialog explaining the OAuth redirect, data usage, and permissions
3

Enter the SQL Warehouse HTTP path

Paste the HTTP path from your Databricks SQL Warehouse connection details (for example, /sql/1.0/warehouses/abcdef1234567890), then select Next.
Connect Databricks dialog step 1 of 2 prompting for the SQL Warehouse HTTP path
4

Enter the SQL Warehouse server hostname

Paste the Server hostname from the same connection details (for example, abc-12345678-wxyz.cloud.databricks.com), then select Continue to Databricks to complete authentication.
Connect Databricks dialog step 2 of 2 prompting for the SQL Warehouse server hostname
5

Configure access

Use Role-Based Access Control to choose which members or groups in your organization can use this connector.
6

Verify the connector is active

Back on the Integrations page, confirm that Databricks (Service Principal) appears under Connectors with an Active connection status.
Replit Integrations page showing the Databricks (Service Principal) connector with an Active connection status

​
Step 4: Build with Agent

After connecting, builders can create applications that use Databricks data with Agent.
1

Start a project

From your Replit home, open the prompt box to start a new project.
Replit home page with the prompt box and Templates dropdown
2

Select the Databricks App template

Open the Templates dropdown and choose Databricks App under Org templates. The prompt is prefilled with instructions that tell Agent how to use your Databricks connector.
Templates dropdown open showing the Databricks App template under Org templates
Add your own prompt after the prefilled instructions to describe what you want to build. For inspiration, browse the Databricks Dev Hub templates.
Prompt box with the Databricks App template selected and prefilled instructions
3

Review and iterate

Review the SQL Agent generates, the tables it queries, and the application structure. Iterate by asking for changes in natural language.

​
Troubleshooting

Verify that the service principal details entered in Replit match the service principal created in Databricks. If credentials were rotated, update the connector in Replit.
The service principal may have metadata access but no read permission on the data. Grant the required table, schema, or catalog permissions in Databricks and try again.
Verify the Server hostname and HTTP path values match the SQL Warehouse connection details in Databricks.