Connect Databricks to Superhuman Docs and Superhuman Go

Superhuman Connectors let you bring the tools your organization relies on directly into Superhuman Docs and Superhuman Go. With the Databricks connector, you can pull data from your Databricks workspace directly into Superhuman Docs and ask questions about it in plain language through Superhuman Go, our AI chat agent — including natural-language Q&A against your Genie Spaces and Unity Catalog data. This ensures that reporting and decision-making are consistently based on your real-time data, allowing your team to derive insights without needing to export spreadsheets or switch tools.

Note: The Databricks connector is only available to customers on our Enterprise tier. You must be an Enterprise admin to complete the setup and configuration steps outlined in this article.

Configure the Databricks connector for your organization

Before the Databricks connector can be used within your organization, an admin must complete a few initial configuration steps. This process has two main parts: creating a service principal in Databricks and configuring the connector in Superhuman.

Part 1: Create a service principal in Databricks

For this next part, you’ll jump over to Databricks. Note that you will need to be a Databricks account or workspace admin in order to follow these steps:

1. Log in to your Databricks workspace (e.g., https://your-workspace.cloud.databricks.com) as an admin.
2. Navigate to Settings (gear icon) → Identity and access → Service principals.
3. Click Add service principal, then Add new.
4. Give it a name (for instance, “Superhuman Docs Databricks Pack”), then click Add.
5. Open the new service principal’s details page, go to the Secrets tab, and click Generate secret.
6. Copy the following pieces of info — you’ll need these for the second part of the configuration:
   • Client ID — the service principal’s Application ID (a UUID).
   • Client Secret — shown once when you generate the secret, so save it securely before closing the dialog.
7. Grant the service principal the permissions your organization wants Docs to have access to. At minimum, it needs:
   • USE CATALOG, USE SCHEMA, and SELECT on the catalogs/schemas it should read from in Unity Catalog.
   • Access to any Genie Spaces it should be able to answer questions from.

Keep this info handy while you go to your Superhuman account to complete the configuration.

Part 2: Configure the connector in Superhuman

With the necessary info from Databricks, you can now complete the configuration in Superhuman:

1. Go to the Connectors page.
2. In the search field in the upper-right corner, enter Databricks, then click on the Databricks connector to start configuring it.
3. On the page that opens, click on the menu next to Connector access and select Custom.
4. In the window that appears, click Confirm.
5. In the Configurations section, click Edit to change the existing configuration, or click + Add Configuration below to create a new one.
6. Enter or edit the configuration name, then under Groups with access, choose whether the configuration applies to everyone or to selected groups.
7. In the Policy section, for the Connection endpoint URL, enter your Databricks workspace URL — the URL you use to access Databricks in the browser (for example, https://your-workspace.cloud.databricks.com).
8. Under Read permissions, select Allow, Always ask, or Deny.
9. Under Write permissions, also select Allow, Always ask, or Deny.
10. Optionally, check the box next to Allow only private connections to write to Databricks.
11. Click on the Select tables… menu and check the box next to Query.
12. Optionally, check the box next to Doc sharing to enforce configuration permissions for it.
13. Next, in the OAuth app credentials section, enter your Client ID and Client secret copied from your Databricks workspace.
14. For the Authorization URL, enter your URL in this format: https://{your-workspace-url}/oidc/v1/authorize
15. For Token URL, enter your URL in this format: https://{your-workspace-url}/oidc/v1/token
16. Click Save configuration.

Note: Databricks doesn’t use individual sign-in like some other connectors. Once an admin completes the configuration above, every member of your organization can start using it right away — there’s no separate “connect your account” step for each person. Superhuman acts using the service principal’s Databricks permissions—the same for everyone using this configuration—so double-check in Part 1 that it only has access to what you want your whole organization to share.

Try out Databricks in Superhuman Docs

After the Databricks connector is configured, you can add it to your doc and start querying your Databricks workspace. To do that, follow these steps:

1. Type /Databricks in your doc, and select the Databricks connector from the options.
2. In the window that appears, click Select configuration, choose a configuration from the dropdown, and click Select. Because there’s no individual sign-in for Databricks, you’re ready to go as soon as you select a configuration.
3. Add a Query table: Find it in the connector settings panel and drag it onto the canvas, or type / followed by the table name on any blank line of your doc.
4. In the panel that opens, select the SQL warehouse and catalog you want to query, then enter your SQL query in the Query field.
5. Select the column(s) used to uniquify each row, then run the query to see the results in Docs.

Tap into Databricks data in Superhuman Go

Superhuman Go is our AI chat agent, available in the Superhuman browser extension for Chrome and Edge, and in the AI editor at app.grammarly.com. Once the Databricks connector is configured, Go can use Databricks’ own Genie — natural-language Q&A over your Genie Spaces and Unity Catalog data — to help you work with your data in plain language, without writing SQL or leaving the page you’re on.

To start Go in the browser, hover over the right edge of your browser window to reveal the Superhuman tab, then click it to open the chat. You can then ask Go to work with your Databricks data. For example, you can:

• Ask questions in plain language: Query your Genie Spaces without writing SQL — for example, “What was total revenue by region last quarter?” — and get an answer grounded in your actual Unity Catalog data.
• Keep a conversation going: Ask follow-up questions, and Go will retain context from earlier turns in the same conversation, just like a normal back-and-forth.
• Pull numbers into your work: Drop specific figures or answers straight into the doc, email, or message you’re drafting.
• Generate content grounded in your data: Turn a Genie answer into a summary, status update, or report without exporting anything first.
• Jump back into Databricks: Every completed answer includes a deep link to the full conversation in the Databricks UI, so you can dig in further.

Because Go uses the context of your active window and connected sources, you can also click Add sources to chat to point it at Databricks before asking your question. Go acts using the service principal’s Databricks permissions—the same for everyone using this configuration—so it can only access the data your organization has chosen to share through the connector.