FINANCE

BigQuery Category Budget Breach to Asana Investigation

Scans spend by GL category in BigQuery on a weekly cadence and, when any category runs over its budgeted burn rate, creates an Asana investigation task with the offending vendors…

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionAggregate spend by GL categoryGoogle BigQueryBigQuery
  • LogicKeep categories over budget pace
  • ActionCreate investigation taskAsanaAsana
  • OutputEmail category ownerGmailGmail

What it does

This workflow rolls up spend by GL category from BigQuery each week and checks each category against its budgeted run rate. When a category is pacing over budget, it spins up an Asana investigation task that lists the top contributing vendors and the size of the overage, then emails the category owner so the dig-in happens before the period closes.

When to use it

Use this when budget owners need a weekly heads-up on which spend categories are running hot and which vendors are driving it. Ideal for FP&A teams that warehouse actuals in BigQuery and track follow-ups in Asana.

How it works

  1. 1A weekly schedule starts the run.
  2. 2A BigQuery query aggregates period-to-date spend per category with each vendor's contribution.
  3. 3A logic step keeps only categories pacing above their budgeted burn rate.
  4. 4An Asana task is created per breached category, listing the driving vendors and the overage.
  5. 5An email goes to the category owner with the task link and a one-line summary.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect AsanaTasks, projects, milestones — everywhere.
  3. 3
    Connect GmailRead, draft, send, label.
  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.