Databricks
Also an agent toolQuery Databricks SQL warehouses directly — lakehouse tables, Unity Catalog and the models your data team publishes, without exporting anything.
3 actions · 1 triggers
The Databricks integration lets you connect Databricks to your automations with 3 actions and 1 triggers — and every action is also a tool an AI agent can call. Examples: Run Query, List Recent Rows, Find By Key. No blank-canvas wiring — connect it and use it in your workflows.
Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.
Triggers 1
Events in Databricks that can start a workflow.
New Row (polling)
Fires for each row added since the last check. Baselines on enable, so existing history does not fire. Point `table` and `cursor_column` at your own table in the trigger's settings.
Actions 3
What Zervanor can do in Databricks.
Run Query
Run a saved SELECT and return its rows.
List Recent Rows
Read the newest rows, newest first.
Find By Key
Look one record up by its key — the read half of a duplicate check.
Nothing matches your search.
Automations using Databricks
Build your own automation with Databricks in the visual builder.
Frequently asked questions
What can I automate with Databricks?
3 actions are available — for example: Run Query, List Recent Rows, Find By Key.
Which Databricks events can start a workflow?
1 triggers — for example: New Row (polling).
Can Databricks be used as an AI agent tool?
Yes. Every Databricks action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.
How is the Databricks integration modelled?
Databricks is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.