DATA OPS

Weekly BigQuery Chargeback Report to a Coda Doc

Each Monday, rolls up the prior week's BigQuery spend by team label into a shareable Coda chargeback doc with week-over-week deltas, then announces the published report in Slack.

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday 7am schedule
  • ActionQuery last week's cost by team with top queriesGoogle BigQueryBigQuery
  • ActionQuery prior week totals for comparisonGoogle BigQueryBigQuery
  • LogicCompute week-over-week deltas per team
  • ActionWrite rollup into Coda chargeback docCodaCoda
  • OutputAnnounce published report in SlackSlack

What it does

Produces a finance-ready weekly chargeback breakdown: total BigQuery cost per team for the last seven days, the change versus the prior week, and top queries per team, written into a structured Coda doc and announced in Slack.

When to use it

When finance does internal chargebacks and needs a clean weekly artifact per team rather than raw query logs. Use it to replace the manual spreadsheet someone rebuilds every Monday.

How it works

  1. 1A scheduled trigger fires Monday at 7am.
  2. 2A BigQuery action queries last week's jobs grouped by team label, returning cost and the top three costliest queries per team.
  3. 3A second BigQuery action pulls the prior week's totals for comparison.
  4. 4A logic step computes per-team week-over-week deltas and percentage change.
  5. 5A Coda action writes the rollup into the chargeback doc's weekly table and appends a dated section.
  6. 6A Slack action posts a link to the freshly published Coda report.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.