Connect Databricks integrations

Verified

Databricks: Run Databricks jobs, clusters, SQL, files, Unity Catalog, and model serving from a workspace, connected to WEXTL workflows and AI agents. Send Databricks deploys, issues and webhook events into your engineering workflows. When Watch Job Runs fires, update the docs, notify a team or continue with Get a Catalog.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • Databricks
  • WEXTL
  • SerpApi
  • LogMeln
  • Google Sheets
  • InstaCharts
  • Cortex
  • Radar
  • Peekalink
  • GitLab
  • ScreenshotOne
  • Hostinger
  • Apify
  • PDF4me
  • Travis CI
  • Dropbox
  • CircleCI
  • tl;dv
  • Mend
  • Lansweeper
  • QuickChart

Supported triggers and actions for Databricks integration

Triggers can detect changes in Databricks and run actions that can create, search or modify data inside Databricks automatically[3], exactly how you set them.

  • Watch Job Runs Checks Databricks on your schedule and starts the workflow once for each new job run, with its Run Id, Run Name, State and Start Time. Use Job to watch one job only, and Since to set where watching starts.
  • Get a Catalog Looks up one Unity Catalog catalog by its Name and returns its details.
  • Get a Cluster Reads the configuration of a single cluster from your workspace.
  • Get a Conversation Message Loads a single message from a Genie conversation, using the space, conversation and message it belongs to.
  • Get a Function Retrieves a Unity Catalog function using its Full Name.
  • Get a Genie Space Reads one Genie space, found by its Space Id, and returns its Id and Name.
  • Get a Job Loads the definition of one job together with its settings.
  • Get a Job Run Retrieves the metadata and details of one job run in Databricks.
  • Get a Job Run Output Fetches the output produced by a single job run in Databricks.
  • Get a Repo Loads one Git repo linked to the workspace.
  • Get a Schema Reads one Unity Catalog schema using its Full Name, along with its details.
  • Get a Secret ACL Reads the permission held by one Principal on a secret scope.
  • Get a Serving Endpoint Reads a model serving endpoint by its Name, including its configuration.
  • Get a SQL Statement Checks a SQL statement, found via its Statement Id.
  • Get a SQL Statement Result Chunk Fetches a single chunk of the result set for a statement, picked with Chunk Index.
  • Get a SQL Warehouse Reads the configuration of one SQL warehouse by its Warehouse Id in Databricks.
  • Get a Table Fetches a Unity Catalog table addressed by its Full Name.
  • Get a Vector Search Index Looks up a vector search index using the Index Name and returns its configuration.
  • Get a Volume Pulls up one Unity Catalog volume found by its Full Name, with its type and location.
  • Get a Workspace Object Status Checks the status of one workspace object, found through its Path.

How to integrate Databricks in automation workflow?

Databricks in three steps: start with "Watch Job Runs", connect one credential, then add your next step.

How Databricks connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Databricks app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Databricks supports.

Full Databricks API documentation

The following table illustrates what fields Databricks integration require during authorization flow inside our workflow builder[4].

Connect Databricks

  • Workspace URL*Text

    ••••••••

  • API Key*Text

    ••••••••

Demonstration of Databricks connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
Workspace URLRequired
text

Workspace origin including protocol, no trailing slash and no /api. Example: https://dbc-a1b2345c-d6e7.cloud.databricks.com. Azure looks like https://adb-xxxx.azuredatabricks.net.

API KeyRequired
password

Settings → Developer → Access tokens. Sent as Authorization: Bearer. Treat it like a password.

Connect Databricks to popular apps on WEXTL

Enter a name of the other app you want to sync with Databricks below. Click on selected app to explore integration options with Databricks. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with Databricks integration

Select Watch Job Runs trigger from Databricks - this will be a starting point in your automation. Whenever event happens in Databricks, workflow will start[7] from Watch Job Runs node.

Search for Create a Job, connect it as the next step of integration sequence. You can use filters between Watch Job Runs and Create a Job, so only important data pass from Watch Job Runs to the next step. WEXTL gives you full control over the process of Databricks automation. All parts of workflow are visible on the canvas[4].

Databricks on WEXTL has 114 modules for creating developer tools automations. Explore Databricks documentation for more.

  • DatabricksWatch Job Runs
  • SerpApiPerforms action

OR

  • SerpApiTriggers
  • DatabricksCreate a Job
Demonstration of how visual Databricks automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating Databricks in your workflows.

What triggers does Databricks support?

Databricks has 1 trigger, including "Watch Job Runs". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in Databricks?

Integration has 113 actions, including "Get a Catalog", "Get a Cluster", and "Get a Conversation Message", and more. Refer to our Databricks Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 113 Databricks modules, like "Get a Catalog", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. Databricks has 2 credential types (1 sign-in, 1 you fill in), and each module uses the one it needs. WEXTL encrypts them at rest, and only your team can use them.

How does WEXTL integrate with Databricks?

Through the official Databricks API: 113 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with Databricks?

Databricks doesn't push events here, so "Watch Job Runs" checks on the schedule you set. Anything Databricks posts to a URL can start a Custom Webhook node.

Why use WEXTL platform for Databricks automation?

WEXTL is an AI-first visual canvas: describe the Databricks flow in plain words and AI wires the nodes[4].

Automate Databricks on WEXTL®

Claim your 3-day trial to build Databricks integrations and access every WEXTL® feature.

Cancel anytime.

References

List of sources used to gather information about the Databricks integration.

  1. Databricks integration source code, module specs and credentials implementation.
  2. Internal Databricks integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official Databricks vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
  5. WEXTL® Apps Library
  6. WEXTL® Databricks App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain Databricks app documentation

Explore how WEXTL® crafted Databricks integration page documentation. Used sources, the role of AI, and how the team validates the result.