Select Databricks in workflow
Pick Databricks app in the workflow builder [4] - just one click to select the app.
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.
3 simple steps to make your Databricks connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
Pick Databricks app in the workflow builder [4] - just one click to select the app.
When prompted, authorize access to Databricks in WEXTL once. Databricks credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Databricks account. Approve?
Build your workflow with Databricks yourself or with WEXTL® AI Builder. Connect Databricks to any available integrations [5], or use HTTP node to go beyond them.
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]. Explore documentation [6] for a detailed list of fields that Databricks supports.
The following table illustrates what fields Databricks integration require during authorization flow inside our workflow builder [4].
Demonstration of Databricks connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
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. |
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.
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 Job, connect it as the next step of integration sequence. You can use filters between Watch Job Runs and Create 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.
Demonstration of how visual Databricks automation [6] looks in WEXTL.
Common questions about automating Databricks in your workflows.
List of sources used to gather information about the Databricks integration.