DATA OPS

Publish a weekly BigQuery slot-cost chargeback report by team to Notion

Every Monday, rolls up the prior week's BigQuery slot consumption by author and maps each author to their team.

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule (prior 7 days)
  • ActionQuery JOBS for slot_ms and bytes by authorGoogle BigQueryBigQuery
  • LogicJoin authors to teams and compute cost deltas
  • ActionWrite per-team chargeback pageNotionNotion
  • OutputUpdate parent rollup page linking teamsNotionNotion

What it does

It produces a weekly, finance-ready chargeback view of BigQuery spend. The workflow aggregates slot-milliseconds and bytes by author, joins authors to teams via a lookup table, converts to dollars, and publishes a structured Notion page per team plus a company rollup.

When to use it

Use it when leadership wants warehouse cost split by team for budgeting or showback, and you'd rather automate the report than rebuild a spreadsheet every Monday. It gives each team lead a single page showing their week-over-week trend and which of their analysts drove the most slots.

How it works

  1. 1A weekly Monday schedule fires for the prior 7 days.
  2. 2Query `INFORMATION_SCHEMA.JOBS` for slot_ms and bytes grouped by user_email.
  3. 3Join authors to teams using a maintained mapping table in BigQuery.
  4. 4Compute per-team dollar cost and week-over-week delta.
  5. 5Create or update one Notion page per team with the trend, top authors, and notable expensive queries.
  6. 6Update the parent rollup page linking all team pages.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.