Databricks (Service Principal) icon

CONNECT APP

Build with Databricks (Service Principal)

Databricks is the lakehouse company, helping data teams solve the world’s toughest problems.

Data Analytics

  • OAuth

MCP

Give your agent Databricks (Service Principal) tools

Every Databricks (Service Principal) action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Databricks (Service Principal) account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "databricks_oauth",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Cancel All Runs:
const result = await mcp.callTool({
  name: "databricks_oauth-cancel-all-runs",
  arguments: {
    jobId: "Job",
    allQueuedRuns: true,
  },
})

API PROXY

Call the Databricks (Service Principal) API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Databricks (Service Principal) API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.example.com/v1/me",
})

// Any allowed Databricks (Service Principal) endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Databricks (Service Principal) actions from your backend

Connect a user's Databricks (Service Principal) account once, then run Cancel All Runs on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "databricks_oauth-cancel-all-runs",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    databricks_oauth: { authProvisionId: "apn_xxxxxxx" },
    jobId: "Job",
    allQueuedRuns: true,
  },
})

TOOLS

Databricks (Service Principal) actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

EVENTS

Databricks (Service Principal) triggers

Event sources your backend can deploy for users and receive through a webhook.

No Databricks (Service Principal) triggers are available yet.

REFERENCE

App details

Reference metadata for the Databricks (Service Principal) connector in the Pipedream registry.

App slug
databricks_oauth
Authentication
OAuth
Categories
Data Analytics
Actions
42
Triggers
0
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed Databricks (Service Principal) OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • all-apis
  • sql