A schedule kicks off an ordered run: ingest your sources, transform with SQL, validate freshness, then deliver. Every run does exactly the same thing — so the numbers your team wakes up to are always current and always agree.
Run on a cron schedule or off an event. Pipelines, models, and refreshes execute in order, with dependencies handled for you.
Watch a metric or a freshness check and get pinged in Slack or email the moment a run fails or a number looks off.
Push results back to the tools your team lives in — Slack, email digests, sheets, or straight into your CRM and other systems.
When configuration isn't enough, drop into a Python step in the same pipeline. No external orchestrator, no glue infrastructure to run.