INVOICE PROCESSING
Invoice OCR → Ledger
Invoices arriving by email are read, line-item extracted, categorized, and filed as structured rows in your database.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice emailGmail
- ActionExtract + categorize
- OutputSave to databaseSupabase
What it does
Pulls invoices from incoming email, extracts vendor / date / totals / line items, suggests a GL category, and writes a structured row to your finance database.
When to use it
AP teams that want receipts and invoices captured without manual data entry.
How it works
Invoice email → extract + categorize → insert to database.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect SupabaseTables, auth, storage, edge functions.
- 3Connect OpenAIModels, embeddings, files.
- 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.
