FINANCE
Agentic triage of anomalous card spend with on-call escalation
An agent investigates card charges that look anomalous — duplicates, spikes, or new high-risk merchants — gathers context, decides severity, and escalates genuine fraud risks…
How it runs
The automated pipeline, trigger to output.
- TriggerAnomalous card charge detectedStripe
- ActionAgent gathers cardholder and duplicate-charge contextStripe
- LogicAgent classifies severity: error, policy, or fraud
- LogicBranch fraud-risk from benign anomalies
- ActionPage on-call finance for fraud riskPagerDuty
- OutputLog investigation and verdict to PostgresPostgres
What it does
When a card charge trips an anomaly signal, an agent investigates it: pulls the cardholder's recent history, checks for duplicate charges, compares the amount to that cardholder's baseline, and researches the merchant. It reasons about whether the charge is a likely error, policy issue, or fraud, then routes accordingly — paging on-call finance for true fraud risk and logging lower-severity findings to Postgres.
When to use it
Use it when simple threshold rules produce too many false alarms and you want judgment applied before anyone gets paged.
How it works
- 1A Stripe webhook delivers a charge that tripped an anomaly threshold.
- 2The agent gathers cardholder history and duplicate-charge context from Stripe.
- 3The agent researches the merchant and reasons about a severity classification.
- 4A logic branch separates fraud-risk from benign anomalies.
- 5An action pages on-call via PagerDuty for fraud risk.
- 6The full investigation and verdict are written to Postgres as the audit output.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
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 Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Overdue Accrual Escalation Emails to Owners and Managers
On a schedule it flags uncoded spend that has stayed open past the chase deadline and emails each delinquent owner via Gmail.
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.