INVOICE PROCESSING
Scan Dropbox contracts for approaching auto-renew dates and alert owners
Daily scans a Dropbox folder of vendor contracts, extracts each auto-renew and notice-period date with AI.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList and download contract PDFs from DropboxDropbox
- ActionExtract dates and owner with OpenAIOpenAI
- LogicKeep contracts with notice window opening in 60 days
- OutputEmail each owner the renewal alert via OutlookOutlook
What it does
Every morning it reads your vendor contract folder in Dropbox, uses AI to pull out the auto-renew date and the notice-to-cancel deadline from each PDF, and flags any contract whose notice window opens in the next 60 days. For each flagged contract it sends the named owner an Outlook email with the vendor, dollar value, key dates, and a one-line recommendation.
When to use it
Use it when contracts live as files in Dropbox and renewals quietly auto-renew because nobody tracks the notice deadline. It turns a pile of PDFs into a dated alert queue so you never miss a cancellation window.
How it works
- 1A daily schedule fires the run.
- 2It lists and downloads new or changed PDFs from the Dropbox contracts folder.
- 3OpenAI extracts vendor name, annual value, auto-renew date, notice-period length, and owner email from each document.
- 4A logic step keeps only contracts whose notice window opens within 60 days.
- 5For each survivor, it sends the owner an Outlook email summarizing the dates and the deadline to act.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect OutlookMail, calendar, contacts.
- 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.
