STEP 1
Connect Cortex 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.
Cortex and Databricks Integration
Connect Cortex 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 Cortex and Databricks
Detailed info you need to know about Cortex and Databricks integrations in WEXTL. Explore which modules apps support and how you connect them.
Databricks
Run Databricks jobs, clusters, SQL, files, Unity Catalog, and model serving from a workspace. [6]
How to connect Cortex to Databricks
Set up your Cortex and Databricks integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cortex 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 Cortex and Databricks. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cortex and Databricks work in WEXTL?
WEXTL exposes actions and triggers for Cortex 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 triggersCortex actions
Databricks modules
- Watch Job RunsTriggers when a Databricks job run starts.
- 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.
Cortex modules
- Delete AnalyzerRemoves a custom analyzer registration.
- Delete JobDeletes a job record.
- Get AnalyzerReturns a single analyzer.
- Get JobReturns a single job.
- Get Job ReportReturns the report for a completed job.
- List AnalyzersRetrieves available analyzers.
- List JobsRetrieves analyzer/responder jobs.
- List RespondersRetrieves available responders.
- Make an API CallPerforms an arbitrary authorized API call.
- Run AnalyzerSubmits an observable to an analyzer.
- Run ResponderRuns a responder against a TheHive entity.
- Submit JobSubmits a file-type observable to an analyzer.
- Update Analyzer ConfigurationUpdates org-level analyzer configuration.
Frequently asked questions
Common questions about connecting Cortex and Databricks.
Connect your Cortex 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 "Delete Analyzer" in Cortex. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); 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. Cortex-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 Cortex (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 Cortex + 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 Cortex and Databricks integration.
- Cortex and Databricks integration source code, module specs and credentials implementation.
- Our Cortex and Databricks integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cortex 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.
- Cortex integration information
- Databricks integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library