FINANCE
Approver Verdict Router: Approve to Books or Reject to Refund
Listens for an approver's decision on a flagged expense via webhook, then routes approved items to a Postgres approved-spend table and rejected items to a Stripe refund…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook with approver verdictHTTP webhook
- LogicBranch on approved vs rejected
- ActionRecord approved charge in PostgresPostgres
- ActionRefund rejected charge via StripeStripe
- OutputNotify employee of outcome in SlackSlack
What it does
This workflow acts on the approver's verdict once a flagged expense has been reviewed. A webhook from your review queue carries the charge ID and the decision. Approved charges are recorded in the Postgres approved-spend table with the approver's name and timestamp, closing the loop for the books. Rejected charges trigger a Stripe refund of the disputed amount and a Slack message to the employee explaining which policy was broken and that the charge is being reversed.
When to use it
Use it as the action half of an expense review pipeline — pair it with a queue that surfaces violations. It removes the manual step of someone copying a verdict into the ledger and separately issuing refunds.
How it works
- 1A webhook delivers the approver's verdict and charge ID.
- 2A branch splits on approved versus rejected.
- 3Approved charges are written to the Postgres approved-spend table.
- 4Rejected charges are refunded through Stripe.
- 5The employee is notified in Slack with the outcome and reason.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect StripeCustomers, subscriptions, payments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Month-End Uncoded Spend Chaser via Snowflake to Slack
On a month-end schedule, queries Snowflake for unaccrued or uncoded expenses, groups them by department owner.
Receipt Upload OCR Policy Check with Manager Escalation
When an employee drops a receipt into a Drive folder, it extracts the line items, checks them against expense policy.
Weekly Proration Anomaly Audit to Notion
Each week it aggregates all flagged proration discrepancies from Snowflake, scores them against anomaly thresholds, and publishes a finance-ready audit page in Notion with totals.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Draft and Send Proration Over-Billing Correction Emails
For each confirmed over-billing credit, an agent drafts a clear, customer-specific apology email explaining the proration error and the credit applied.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.