Late payments quietly strangle small businesses. Most SMB cash-flow problems trace back to invoices that sit unpaid for weeks — not because clients refuse to pay, but because nobody reminded them. Chasing invoices by hand is awkward, easy to forget, and the first thing that slips when you’re busy. This tutorial shows you how to automate the whole thing with n8n, the popular workflow automation tool, plus a touch of AI to draft polite, personalized reminder emails.
The workflow runs every morning: it scans your invoice list, finds every unpaid invoice past its due date, drafts a tailored reminder with AI, and sends it automatically. Set it up once, and you’ll never forget a follow-up again.
Prerequisites
You don’t need to be a developer, but you should be comfortable connecting accounts and following a recipe. Have these ready:
- An n8n account. n8n offers hosted n8n Cloud (with a free trial) or a free self-hosted Community Edition. A daily reminder workflow burns one execution per day, so the cheapest plan covers most small businesses.
- An invoice list in Google Sheets. Export your invoices from QuickBooks, Xero, Wave, or any accounting tool into a Google Sheet with columns: Invoice number, Client name, Client email, Amount, Due date, Status (Paid/Unpaid).
- A Gmail account (or any SMTP service) to send from.
- An OpenAI API key for the AI drafting step — pay-as-you-go usage costs a few cents per reminder.
How the workflow works
The chain: Schedule Trigger → Google Sheets → IF (overdue?) → OpenAI (draft) → Gmail (send) → Google Sheets (log). Here is each node.
Step 1: Create the workflow and add a Schedule Trigger
Add a Schedule Trigger node first and set it to run every weekday morning at 9 AM — daily is plenty; you don’t want to spam anyone. Use Execute step to watch the chain fire while building.
Step 2: Read your invoice list with the Google Sheets node
Add a Google Sheets node and connect your Google account (n8n walks you through OAuth — credentials stay in n8n, never in the workflow). Set it to read rows from your invoices sheet. Keep two extra columns: Last reminder sent and Reminders count — steps 6 and 7 depend on them.
Step 3: Filter to overdue, unpaid invoices with an IF node
Add an IF node: Status = Unpaid AND Due date before today (reference row values with expressions like {{ $json.due_date }}). Also skip rows where Last reminder sent was today — no double-sends — and rows with a Hold flag for clients you’re negotiating with manually.
Step 4: Draft a personalized reminder with the OpenAI node
Add an OpenAI node (text generation) before the send step — this is where the AI earns its keep. Give it a prompt like: “Write a short, polite payment reminder email. Client: {{ $json.client_name }}, invoice {{ $json.invoice_number }}, amount {{ $json.amount }}, {{ $json.days_overdue }} days overdue. Under 120 words, friendly but clear.” The draft names the client, the amount, and the lateness — far less robotic than a canned template — and you pipe it straight into the email body.
Step 5: Send it with the Gmail node
Add a Gmail node, connect your account, and send to {{ $json.client_email }}. Put the AI draft in the body with a clear subject: “Friendly reminder: Invoice {{ $json.invoice_number }} ({{ $json.amount }}) due {{ $json.due_date }}”.
Step 6: Log the reminder back to the sheet
Add a second Google Sheets node to update the row: stamp today’s date in Last reminder sent and increment Reminders count. Step 3’s guard clause uses this log to prevent duplicates.
Step 7: Add a gentle escalation path
Not every client pays after one nudge. Route invoices by Reminders count: the first reminder stays friendly; at 14 days overdue, switch to a firmer prompt (“state that services may be paused”); at 30 days, stop emailing and alert yourself by Slack or email to call the client personally. Automation handles the routine 90% — a human handles the difficult 10%.
Step 8: Test with your own email, then activate
Before touching real clients, point the recipient at your own address and run Execute workflow end-to-end. Check tone, amounts, and that expressions resolved to real values — then flip the recipient back, save, and click Active.
Pricing
n8n itself is free to start. The Community Edition is free to self-host (fair-code license) — you pay only for the server. n8n Cloud is priced in euros by monthly workflow executions, not by users: as listed on n8n.io/pricing, Starter covers 2,500 executions, Pro 10,000, Business 40,000, Enterprise custom — with unlimited users and workflows on every plan. This reminder workflow runs once a day (about 30 executions a month), so the cheapest plan has enormous headroom. Prices change, so check n8n.io/pricing before you buy. The only other cost is OpenAI API usage — pay-as-you-go, well under a dollar a month for a small client list.
If you’re weighing automation platforms overall, our AI tools pricing index tracks what popular business AI tools cost, and our n8n workflow tutorial covers more general automation ideas for the same platform.
Tips and common mistakes
- Start with send-to-self testing. Route the first week’s runs to your own inbox to catch bad expressions, wrong dates, and off-tone AI drafts before any client sees them.
- Respect the “hold” list. Clients with active disputes, payment plans, or paused projects should never get automated reminders. A Hold column in your sheet, checked in step 3, prevents embarrassing emails.
- Keep humans on the big invoices. For your largest invoices, have the workflow send the AI draft to you for a quick review instead of auto-sending. Two minutes on a $20,000 invoice is worth it.
- Watch email limits. Gmail caps daily sending. If you send hundreds of reminders, switch the Gmail node to a transactional service like SendGrid or Amazon SES.
- Don’t email on day one. Send the first reminder 1–3 days after the due date, not on it. A same-day reminder reads as aggressive.
- One execution per run. n8n counts a complete workflow run as one execution regardless of invoice count — this daily job barely dents your quota.
Who should and shouldn’t use this
Ideal for freelancers, agencies, and small service businesses that invoice on 14–30 day terms. If your accounting tool can export to a spreadsheet, you can build this in an afternoon.
Skip it (for now) if your accounting platform’s built-in reminders already work for you — or if you have so few invoices that five personal emails a month take ten minutes. Automation has to beat the manual alternative, not just feel clever.
Verdict
Automating invoice reminders is one of the highest-ROI automations a small business can build: one afternoon of setup, pennies a month to run, and it directly shortens the time between “invoice sent” and “money in the bank.” The n8n + AI combination hits a sweet spot — the workflow handles the boring scheduling and sending, while the AI makes each reminder read like you wrote it personally.
FAQ
Do I need to know how to code to build this n8n workflow?
No. Everything in this tutorial uses n8n’s visual nodes and point-and-click expressions. The only “code” involved is short field references like {{ $json.client_name }}, which n8n helps you insert.
Can I use this with QuickBooks or Xero instead of Google Sheets?
Yes — both have n8n integrations, and all major accounting tools export CSV. Start with the Google Sheets version to learn the pattern, then swap in a direct integration later.
Is n8n really free?
The Community Edition is free to self-host — you only pay for your server. n8n Cloud is paid hosting priced by monthly executions, with a free trial.
Won’t AI-generated reminders sound robotic?
Not if you prompt it well. Because the draft includes the client’s name, the real invoice number, the amount, and how many days overdue it is, it reads like a careful personal email. Always test the drafts on yourself first and adjust the prompt until the tone fits your business.
What happens if a client pays but the sheet isn’t updated?
It would keep reminding them — so update invoice statuses on the same schedule the workflow runs. Mark invoices paid in your accounting tool and re-export or sync the sheet before each run.
