STEP 1
Connect Azure Storage and Databricks
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Azure Storage and Databricks Integration
Connect Azure Storage and Databricks to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Azure Storage and Databricks
Detailed info you need to know about Azure Storage and Databricks integrations in WEXTL. Explore which modules apps support and how you connect them.
Azure Storage
Manage containers and blobs in Azure Blob Storage. [5]
Databricks
Run Databricks jobs, clusters, SQL, files, Unity Catalog, and model serving from a workspace. [6]
How to connect Azure Storage to Databricks
Set up your Azure Storage and Databricks integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Azure Storage and Databricks nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Azure Storage and Databricks. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Azure Storage and Databricks work in WEXTL?
WEXTL exposes actions and triggers for Azure Storage and Databricks that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Databricks triggersAzure Storage actions
Databricks modules
- Cancel All RunsCancels all runs of a job.
- Cancel RunCancels a job run.
- Cancel SQL StatementCancels a SQL statement.
- Change Cluster OwnerChanges the owner of a cluster.
- Create CatalogCreates a catalog.
- Create ClusterCreates a new cluster.
- Create Conversation MessageSends a message in a Genie conversation.
- Create DirectoryCreates a volume directory.
- Create FunctionCreates a function.
- Create JobCreates a new job.
- Create RepoCreates a new repo.
- Create SchemaCreates a schema.
- Create Secret ScopeCreates a secret scope.
- Create Serving EndpointCreates a serving endpoint.
- Create SQL WarehouseCreates a SQL warehouse.
- Create Vector Search IndexCreates a vector search index.
- Create VolumeCreates a volume.
- Create Workspace DirectoryCreates a workspace directory.
- Delete CatalogDeletes a catalog.
- Delete Cluster PermanentlyPermanently deletes a cluster.
- Delete DirectoryDeletes an empty volume directory.
- Delete FileDeletes a file from a Unity Catalog volume.
- Delete FunctionDeletes a function.
- Delete JobDeletes a job.
- Delete RepoDeletes a repo.
- Delete RunDeletes a job run.
- Delete SchemaDeletes a schema.
- Delete SecretDeletes a secret.
- Delete Secret ACLDeletes a secret ACL.
- Delete Secret ScopeDeletes a secret scope.
- Delete Serving EndpointDeletes a serving endpoint.
- Delete SQL WarehouseDeletes a SQL warehouse.
- Delete VolumeDeletes a volume.
- Delete Workspace ObjectDeletes a workspace object.
- Download FileDownloads a file from a Unity Catalog volume.
- Edit ClusterEdits an existing cluster.
- Edit SQL WarehouseEdits a SQL warehouse.
- Execute Message SQL QueryExecutes the SQL query on a Genie message attachment.
- Execute SQL StatementExecutes a SQL statement on a warehouse.
- Export RunExports a job run.
- Export Workspace ObjectExports a workspace object.
- Get CatalogReturns a catalog.
- Get ClusterReturns a single cluster.
- Get Conversation MessageReturns a Genie conversation message.
- Get File MetadataReturns metadata for a volume file.
- Get FunctionReturns a function.
- Get Genie SpaceReturns a Genie space.
- Get JobReturns a single job.
- Get Job RunReturns a single job run.
- Get Job Run OutputReturns output for a job run.
Azure Storage modules
- Copy BlobCopies a blob server-side.
- Create ContainerCreates a new storage container.
- Delete BlobDeletes a blob.
- Delete ContainerDeletes a container and all blobs it contains.
- Get BlobDownloads a blob.
- Get Blob PropertiesReturns blob properties from response headers.
- Get Container MetadataReturns container metadata from response headers.
- Get Container PropertiesReturns container properties from response headers.
- List BlobsRetrieves blobs in a container.
- List ContainersRetrieves storage containers.
- Make an API CallPerforms an arbitrary authorized API call.
- Set Blob MetadataReplaces user-defined blob metadata.
- Set Blob TierChanges the access tier of a blob.
- Set Container MetadataReplaces user-defined container metadata.
- Upload BlobUploads a block blob.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Azure Storage and Databricks integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Azure Storage and Databricks.
Connect your Azure Storage and Databricks accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Databricks's "Watch Job Runs" fires, WEXTL can "Copy Blob" in Azure Storage. Azure Storage has 15 actions (including Copy Blob, Create Container, and Delete Blob); Databricks has 113 actions (including Cancel All Runs, Cancel Run, and Cancel SQL Statement). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Azure Storage-to-Databricks automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Azure Storage (or Databricks) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Azure Storage + Databricks automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Azure Storage and Databricks integration.
- Azure Storage and Databricks integration source code, module specs and credentials implementation.
- Our Azure Storage and Databricks integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Azure Storage and Databricks — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Azure Storage integration information
- Databricks integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library