The Transforms tab runs, schedules, and watches your dbt project — and when something breaks, the agent diagnoses it against your live schema, ships the fix as a diff, and re-runs. Not just an orchestrator: a colleague.
Live miniature, open on dbt Transforms — the agent just fixed the nightly run. Click the fixed model for the diff, or read the chat on the right.
Point Mako at your dbt repo and you get scheduled runs, per-model status and timing, logs, and lineage out of the box. Everything you'd expect from a hosted orchestrator, next to the same warehouse connections your Consoles and Flows already use.
A renamed column upstream, a type change in a source, a test that started failing at 3am — the agent reads the error, the model SQL, and your actual warehouse schema, then proposes a concrete diff. You review it; it re-runs the affected models and reports back in the chat.
Describe the metric you need and the agent drafts the dbt model — staging, intermediate, and mart — following the conventions already in your project. It knows your sources because it synced them, and your schema because it queries it every day.
“The agent fixed our nightly dbt run before I'd finished my caf. I felt a great disturbance in the on-call rotation.”
Connect your repo, schedule a run, and let the agent take the 3am pages.