Invoice Chaser
Chase overdue invoices without writing a single reminder.
Every weekday morning it reads your invoice sheet, finds the unpaid invoices that are overdue and drafts a reminder for each one in a tone that suits the delay. Every reminder waits in your Gmail drafts, so you read it and press send yourself.
A real customer situation
A bakery supplies a dozen cafés on 14-day terms. Three invoices are late, one by more than a month, and the owner only finds out when she sits down with the books on a Sunday night and has to write each reminder from scratch.
Where the owner wants to be
Each morning the owner opens Gmail to a short pile of ready reminders, friendly for a few days late, firm after two weeks and a final notice after a month. She checks them, sends the ones she agrees with, and the sheet shows who was chased and when.
What it handles
- Reads the invoice sheet every weekday at 08:00 and finds overdue, unpaid invoices
- Matches the tone to the delay: friendly from 3 days, firm from 14, final notice from 30
- Saves each reminder as a Gmail draft with the invoice number and amount copied from the sheet
- Writes the draft date back to the sheet so no invoice is chased twice within 7 days
- Flags invoices with no email, and any still unpaid after a final notice, to the owner
What it deliberately does not do
- Never sends an email: every reminder is a draft until the owner sends it
- Never changes an amount, a due date or a payment status
- Never chases the same invoice twice within 7 days
- Drafts one final notice per invoice; anything after that is the owner's decision
Live agent
Try the real agent
This runs the actual n8n workflow and Claude, not a simulation. Pick a sample invoice and have the reminder emailed to you, or type your own invoice and see the draft here. Either way the agent decides whether to chase, picks the tone and writes the reminder. Nothing is ever sent to the client on the invoice.
What the agent did
Pick a sample invoice, add your email and press Send. If a reminder is due, you will receive exactly what the client would get. If it is not due, the agent tells you why and sends nothing.
Interactive demo
Try it with sample data
No sign-up needed. Pick a scenario, change the inputs, then play the customer and the owner. The right-hand panel only shows what the workflow actually recorded.
Uses a sample invoice sheet for a fictional bakery and a simulation clock. Drafts stay in an on-screen outbox; no email is sent and no real sheet is changed.
Choose a scenario
INV-1042 is 5 days late and has never been chased, so it gets a friendly draft.
Friendly from 3 days late, firm from 14, final notice from 30.
Never chased twice within 7 days.
Customer side · Morning summary to the owner
Press “Run scenario” to start. Every message and record here comes from sample data.
Workflow and harness
How Invoice Chaser runs
Reference schematic for the proposed workflow. Blue steps do the work, purple paths handle exceptions and returns, and amber checks are the harness controls that a step cannot pass without.
Overview — business stages
Read the full flow as text
- Weekday 08:00 run (business step)
Monday to Friday at 08:00. Output: Run started. Leads to: Read invoice sheet. - Read invoice sheet (business step)
Client, email, amount, due date, status, last chased. Output: Invoice list. Leads to: Find overdue unpaid invoices; Missing email (no email). - Find overdue unpaid invoices (business step)
Unpaid and at least 3 days past due. Output: Invoices to chase. Leads to: Choose tone by delay; Paid or not yet due (skip); Chased in the last 7 days (too soon). - Choose tone by delay (business step)
Friendly 3+, firm 14+, final notice 30+. Output: Tone per invoice. Leads to: Save reminder as Gmail draft. - Save reminder as Gmail draft (business step)
One draft per invoice per day. Output: Gmail draft. Leads to: Write draft date to sheet. - Write draft date to sheet (business step)
Set last chased to today. Output: Updated row. - Missing email (exception or return path)
No draft; ask the owner to add one. Output: Owner flag. - Paid or not yet due (exception or return path)
Skip this run. Output: No action. - Chased in the last 7 days (exception or return path)
Hold until 7 days have passed. Output: Held invoice. Leads to: Weekday 08:00 run (next run). - No repeat within 7 days (harness check)
Block if chased less than 7 days ago. Output: Allow / hold. Leads to: Find overdue unpaid invoices (required check). - Amount unchanged (harness check)
Amount and invoice number copied, never edited. Output: Pass / block. Leads to: Choose tone by delay (required check). - Draft only, never send (harness check)
Saved to Gmail drafts; the owner sends. Output: Draft. Leads to: Save reminder as Gmail draft (required check).
Harness controls
- Draft only: the workflow has no step that can send an email
- Copy the amount and invoice number from the sheet and check them before saving
- Skip any invoice chased in the last 7 days
- Use a draft key per invoice and day so a retried run never creates a second draft
- Stop after one final notice and hand the invoice to the owner
Systems and data
Production reads a Google Sheet, writes reminders with a model and saves them as Gmail drafts. The demo uses a fictional bakery's five-row invoice sheet, a simulation clock and an outbox that holds every draft.
Demo boundary
External calls, customer messages, payments and business writes use synthetic fixtures and an on-screen outbox. The demo shows only verified demo state. Custom production connections are a paid implementation deliverable.
What gets delivered
The records your business receives
Gmail draft
A reminder addressed to the client, quoting the invoice number, amount and days overdue, in the tone that matches the delay.
Sheet update
The invoice's last-chased column set to the draft date, so tomorrow's run knows to leave it alone.
Owner flag
A short note when an invoice has no email on file or is still unpaid after a final notice.
Custom deployment
Configured for your business during a paid implementation. Integrations are confirmed during discovery, never assumed.
Your business rules
- Grace period and the days that switch the tone to firm and final
- Minimum gap between reminders for the same invoice
- Wording and sign-off for each tone
- Which sheet columns hold the client, email, amount, due date, status and last-chased date
Systems we connect
Measurement
We measure completed business against a baseline, not messages sent. No results are promised before discovery.
Business results
- Days sales outstanding
- Value of invoices more than 30 days overdue
- Owner time spent chasing each week
Operational reliability
- Emails sent by the agent (target: zero)
- Reminders with an amount that differs from the sheet (target: zero)
- Invoices chased twice within 7 days (target: zero)
Want this drafting reminders for your own unpaid invoices?
Book a call about Invoice Chaser. We start with discovery: your current process, volumes, systems and who handles exceptions. The proposal then defines the integrations, approvals and acceptance tests before anything goes live.