agent hive

FINANCE

Weekly Expense Violation Digest with Category Trends

Each week, aggregates resolved and pending policy violations from Postgres, summarizes the top offending categories and repeat employees.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionAggregate last 7 days of violations from PostgresPostgreSQLPostgres
  • ActionDraft trend digest with OpenAIOpenAI
  • ActionPublish dated digest page to NotionNotionNotion
  • OutputPost summary and link to finance Slack channelSlack

What it does

This workflow gives finance leadership a weekly read on expense-policy health. On a weekly schedule it pulls the past seven days of violations from the Postgres review table, then uses OpenAI to write a plain-language summary: total flagged spend, the categories generating the most violations, repeat offenders, and how the week compares to the prior one. The digest is published as a dated Notion page for the record and posted to the finance Slack channel for visibility.

When to use it

Use it when individual violation alerts are handled day to day but no one has the bird's-eye trend — which categories keep slipping, whether tightening a cap would help, and who needs coaching.

How it works

  1. 1A weekly schedule starts the run.
  2. 2A Postgres query aggregates the last seven days of violations.
  3. 3OpenAI drafts a digest with trends and repeat offenders.
  4. 4The digest is saved as a dated Notion page.
  5. 5A summary with the Notion link is posted to the finance Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.