FINANCE

Daily BigQuery Cloud-Spend Anomaly Digest to Finance Discord

Runs a scheduled BigQuery query against your billing export each morning, detects yesterday's spend anomalies versus a rolling baseline.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule at 8am finance timezone
  • ActionQuery yesterday spend vs 14-day baseline in BigQueryGoogle BigQueryBigQuery
  • LogicFilter to services exceeding threshold
  • ActionNarrate anomalies in plain EnglishOpenAI
  • OutputPost digest to finance Discord channelDiscordDiscord

What it does

Every morning this workflow queries your GCP billing export in BigQuery, compares yesterday's per-service spend against a 14-day rolling average, and flags any line item that exceeds its baseline by a configurable threshold. It then asks an LLM to narrate the findings in clear finance-team language and posts the digest to Discord so the team starts the day knowing where the money went.

When to use it

Use it when your cloud bill is large enough that surprises hurt but small enough that nobody is staring at billing dashboards daily. It replaces the manual morning ritual of exporting CSVs and eyeballing totals, and gives finance an audit trail of what changed and by how much.

How it works

  1. 1A daily schedule fires at 8am in your finance timezone.
  2. 2A BigQuery query pulls yesterday's cost grouped by service alongside the trailing 14-day average per service.
  3. 3A logic step keeps only services whose spend rose more than the threshold percentage.
  4. 4If nothing crossed the threshold, the run posts a short "all clear" note and exits.
  5. 5OpenAI turns the flagged rows into a readable summary with dollar deltas and likely drivers.
  6. 6The narrated digest is posted to the finance Discord channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect DiscordCommunity channels + voice + bots.
  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.