INVOICE PROCESSING
Price-Creep Investigator and Dispute-Email Drafter
When a flagged price increase is escalated, an agent researches the vendor contract terms, confirms whether the hike violates agreed caps.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator escalates flagged increase via webhookHTTP webhook
- ActionRetrieve governing vendor contractGoogle Drive
- LogicCheck new rate against price-cap and notice clauses
- LogicBranch clear breaches from gray-area cases
- OutputSave grounded dispute email as Gmail draftGmail
What it does
This is the agent-driven follow-up to a detected price increase. Given a flagged invoice, it reads the governing vendor contract, checks whether the new rate breaches any agreed price-cap or notice clause, and composes a professional dispute email citing the exact contract terms. The draft is staged for a human to review before sending.
When to use it
Use this when a silent increase has been confirmed and you want to push back, but writing each dispute by hand is slow. It turns a flag into a ready-to-send, contract-grounded challenge while keeping a human in the loop on tone and final send.
How it works
- 1A webhook fires when an operator escalates a flagged increase.
- 2The agent retrieves the vendor's contract document from Google Drive.
- 3It analyzes the new rate against the contract's price-cap and notice clauses, reasoning over whether the hike is permissible.
- 4A logic branch separates clear breaches from gray-area cases needing manual judgment.
- 5For breaches, the agent drafts a dispute email referencing the specific clause and the rate history.
- 6The draft is saved to Gmail as a reviewable draft for human approval and send.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect GmailRead, draft, send, label.
- 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 Invoice Processing workflows
Nightly audit that flags duplicate payments already made
Runs every night to scan the last 90 days of Stripe payments against your Postgres invoice ledger.
Agent that codes Front invoices to GL accounts and drafts a bill
An agent reads each Front vendor invoice, assigns GL account codes per line item using your chart of accounts and past coding history.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
Gate invoice approvals on a duplicate cross-check
When an approver clicks Approve in your AP system, a webhook re-validates the invoice against paid history in Postgres and Stripe charges.
Catch duplicate invoices as they hit your AP inbox
Watches your accounts-payable Gmail inbox for incoming invoice emails, fingerprints each one, and routes likely duplicates to a review label instead of into the approval queue.
Block duplicate Stripe payouts before they send
When a new vendor invoice is queued for payment in Stripe, cross-check it against your paid-invoice history in Postgres and halt any payout that matches an already-paid invoice.
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.