Connectors / Databricks
What Deixic does with Databricks.
Read and act
Find workspace resources and data behind an analysis task.
How Deixic helps with Databricks.
- Read information
- Review clusters, jobs and warehouses from Databricks as evidence and to check state.
- Choose the actions
- Deixic supports actions on jobs. Grant only the tools and permissions the task needs.
- Keep your decisions
- Deixic checks your policy before a change; sensitive changes wait for a named approver. The action record keeps the decision and result.
2 of 2 changing operations require approval. See how approvals work.
Example workflow
Build an operational brief before changing a data workflow
Review the authorized Databricks jobs, pipelines, clusters, and warehouses relevant to this task. Identify the objects involved and any information still needed to diagnose the issue.
- Identify the job or pipeline by its stable identifier. Retain the workspace context so similarly named jobs in different environments are not treated as the same object.
- Read the relevant cluster, warehouse, and instance-pool information. Separate configuration from a conclusion about execution: the existence of a job does not establish that its latest output is correct.
- Prepare a handoff with the affected identifiers, the observed configuration, and the next diagnostic question. These connector capabilities are reads; changes or execution need a separately authorized path.
Check before you continue: An inventory is useful for locating the problem, but is not a substitute for examining the execution or output that failed. Keep those two kinds of evidence distinct in the brief.
Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.
Provider access
Supported Databricks reads and actions.
Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.
Read data
- Clusters Read
- Jobs Read
- Warehouses Read
- Pipelines Read
- Instance Pools Read
Actions
- Jobs Write
Permissions
Choose the access for Databricks.
Use a token issued for the account the agent should work in, check its owner, expiry, and resource access, and remember that replacing an expired token does not change the account’s permissions.
Find Databricks in the appManage connected accounts
- Connection
- Bearer token
- Supported operations
- Read and act
- Reads
- 5
- Actions
- 1
- Provider permissions
- Grant only the permissions needed for the task.
What you need to connect
- Workspace host
- Personal access token
Deixic checks calls routed through its gateway and requests approval when your policy requires it.
Reference and troubleshooting
Databricks operation reference, troubleshooting, and questions
Guides for work in Databricks
Your agent found a green status. Did the work actually finish?
Use Vercel deployment and Databricks job information to investigate the right environment, separate execution from outcomes, and avoid repeated recovery actions.
Connectors for related work
Tell us what you need from Databricks.
Bring one task. We’ll show you the access it needs and how Deixic helps.
Request early access