Databricks workspace automation
Databricks is the lakehouse platform where data teams run Spark jobs, query SQL warehouses, and govern data through Unity Catalog. The NoClick Databricks node speaks the Databricks REST API, so a single workflow can spin up clusters, apply cluster policies, cancel running jobs, commands, and SQL statements, create catalogs, connections, and external locations, and check whether a table exists before it writes. It also fires triggers on job run events, so a run starting, succeeding, failing, or overrunning its expected duration can kick off downstream work. Add it to the canvas to turn platform housekeeping and job monitoring into automation instead of manual console clicks.
Yes. The Databricks node creates clusters, creates cluster policies, changes a cluster's owner, and reports library install status for a cluster. You can attach these to any trigger, so a schedule, a form submission, or a job event can provision and configure compute without touching the workspace UI.
Yes. The node ships triggers for job runs starting, succeeding, and failing, plus an any-job-event trigger and one that fires when a run exceeds a duration threshold. The trigger starts your workflow with the run details, so you can cancel remaining runs, send an alert, or retry the work on a new cluster.
The node creates catalogs, connections, and external locations, and it can check whether a specific table exists before you write to it. That lets a workflow stand up governance objects on demand instead of setting them up by hand for each new dataset.
Yes. The node cancels a specific job run, cancels all runs at once, cancels a running command, and cancels a SQL statement. Wire it to the duration-threshold trigger or an AI step and a workflow can stop a runaway query or job on its own.
Add the Databricks node and provide your workspace host along with an access token, which authenticates against the Databricks REST API for that workspace. Once connected, every operation in the node runs against your workspace, including the cluster, job, SQL, and catalog actions.