DATA OPS
Weekly Warehouse Cost Digest to Notion with AI Owner Notes
Every Monday, pulls the prior week's BigQuery and Snowflake credit spend by owner, uses an LLM to write a plain-English summary of who drove the change and why.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionPull last week's spend per owner from BigQueryBigQuery
- ActionPull last week's credit spend per owner from SnowflakeSnowflake
- LogicMerge platforms, compute deltas, find top movers
- ActionGenerate plain-English cost digest with LLMOpenAI
- OutputPublish digest as a Notion pageNotion
What it does
It produces a weekly cross-warehouse cost digest spanning both BigQuery (slot/bytes) and Snowflake (credits). It attributes each platform's spend to owners, compares against the prior week, and uses an LLM to narrate the top movers — who grew, by how much, and the likely driver based on their query mix — then publishes a clean, shareable Notion page for the data and finance teams.
When to use it
Use it when you run more than one warehouse and want a single readable weekly artifact instead of two raw dashboards. The AI narration turns numbers into an explanation a non-engineer can act on.
How it works
- 1A weekly Monday schedule fires.
- 2BigQuery returns last week's spend per owner with prior-week comparison.
- 3Snowflake returns last week's credit spend per owner with prior-week comparison.
- 4A logic step merges both platforms into one per-owner table and identifies top movers.
- 5An LLM writes a plain-English digest explaining the biggest changes.
- 6The digest is published as a new Notion page in the FinOps space.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.