DOCUMENT OPS

Weekly expense rollup digest to Slack

Every Monday, aggregates the prior week's receipt records in BigQuery by category and submitter, and posts a spend summary with top vendors and outliers to a Slack finance channel.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires Monday morning
  • ActionRun weekly aggregation queries in BigQueryGoogle BigQueryBigQuery
  • LogicFlag week-over-week swing vs. trailing average
  • OutputPost formatted spend digest to SlackSlack

What it does

Delivers a recurring, plain-language view of receipt spend. On a weekly schedule it runs aggregation queries over the BigQuery expense ledger, rolling up totals by category, submitter, and vendor for the previous week, then formats the result into a readable Slack digest with notable jumps highlighted.

When to use it

Use it when leadership wants a steady pulse on expenses without opening a dashboard. It is the routine that replaces the manual Monday spreadsheet someone used to assemble from receipt data.

How it works

  1. 1A weekly schedule trigger fires Monday morning.
  2. 2An action runs BigQuery aggregation queries for the prior week: total spend, breakdown by category, top five vendors, and largest single receipts.
  3. 3A logic step compares the week's total against the trailing four-week average to flag any meaningful swing.
  4. 4The numbers are formatted into a concise Slack message with the swing called out when present.
  5. 5The digest posts to the finance Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.