FINANCE

Log BigQuery Spend Anomalies to Airtable and Notify Discord

Detects daily BigQuery spend anomalies, writes each one as a triageable record in an Airtable tracker, and posts a Discord summary linking back to the new rows for follow-up.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery per-service spend vs baseline in BigQueryGoogle BigQueryBigQuery
  • LogicFilter to anomalies above threshold
  • ActionCreate anomaly records in Airtable trackerAirtableAirtable
  • ActionSummarize the batchOpenAI
  • OutputPost linked summary to finance DiscordDiscordDiscord

What it does

This workflow turns spend anomalies into trackable work items. Each morning it finds services that overran their baseline, logs every anomaly as a structured row in an Airtable base with the service, dollar delta, date, and a status field, then posts a Discord summary that links to the new records so an owner can claim and resolve them.

When to use it

Use it when detection alone is not enough and you need accountability: a recurring monthly cost review, a FinOps practice that wants a backlog of anomalies to investigate, or any team that wants to track which spend surprises were explained versus genuinely wasteful.

How it works

  1. 1A daily schedule triggers the run.
  2. 2A BigQuery query returns yesterday's per-service spend against its rolling baseline.
  3. 3A logic step keeps only rows above the anomaly threshold.
  4. 4Each flagged anomaly is created as a record in the Airtable anomaly tracker with status set to New.
  5. 5OpenAI summarizes how many anomalies were logged and the largest dollar movers.
  6. 6The summary posts to the finance Discord channel with a link to the Airtable view.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect DiscordCommunity channels + voice + bots.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.