Databricks

Install corsair and @corsair-dev/databricks, add the Databricks plugin, and connect with an API key or OAuth. Then call methods like corsair.databricks.api.apps.createDatabricksApp() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. Databricks supports an API key or OAuth. Use credentials or OAuth scopes that match what you automate. Create them in the Databricks developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Databricks, GitHub, Notion, Stripe, and the rest. Trigger Databricks from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for unified data and ai platform for lakehouse analytics, notebooks, and machine learning. Common builds include sync jobs, admin tooling, and agents that call Databricks APIs from your backend. Local DB entities let you query synced Databricks records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Databricks API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/databricks in the open repo. When Databricks ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Databricks data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Databricks data on your behalf.