Overview
Late payments are one of the biggest cash-flow problems for small businesses, yet most owners send reminders inconsistently because it's awkward and time-consuming. This n8n workflow runs on a daily schedule, queries your accounting tool (QuickBooks, Xero, or FreshBooks) for unpaid invoices past their due date, and automatically sends a tiered sequence of reminder emails — a gentle nudge at 3 days, a firmer reminder at 14 days, and an urgent notice at 30 days. Each email is personalized with the client name, invoice number, amount, and a payment link. The workflow also logs each reminder to a Google Sheet for audit purposes.
Before you start
- n8n Cloud or self-hosted n8n
- QuickBooks Online, Xero, or FreshBooks account with API access
- Gmail account or SMTP email credentials
- Google Sheets for reminder logging (optional but recommended)
Step-by-step guide (5 steps)
Create a Schedule trigger to run daily
Add a Schedule Trigger node set to run every day at 9:00 AM in your local timezone. This ensures reminders go out at the start of the business day when clients are most likely to act on them.
Fetch overdue invoices from your accounting tool
Add a QuickBooks Online, Xero, or FreshBooks node set to 'Get All Invoices'. Filter for status = 'Unpaid' and due date before today. The node will return all overdue invoices with client name, email, invoice number, amount, and due date.
Use n8n's Date & Time node to calculate 'days overdue' by subtracting the due date from today's date — this value drives the escalation logic.
Add escalation logic with a Switch node
Add a Switch node with three conditions: 1–7 days overdue routes to a Tier 1 friendly email, 8–21 days overdue routes to a Tier 2 firm email, and 22+ days overdue routes to a Tier 3 urgent email. Write three different email templates, each referencing the invoice details from the previous node.
Send personalized reminder emails via Gmail or SMTP
Add a Gmail node (or SMTP node) on each Switch branch. Set the 'To' field to the client's email, the subject to 'Invoice #[number] — Payment Due', and the body to the appropriate template. Include the invoice amount, original due date, days overdue, and a payment link pulled from the accounting node.
Avoid words like 'Final Notice' until 30+ days — premature urgency damages client relationships.
Log each reminder to Google Sheets for your records
Add a Google Sheets node after each email branch set to 'Append Row'. Log the date, client name, invoice number, amount, days overdue, and which tier reminder was sent. This creates an audit trail for disputes and helps you identify habitually late-paying clients.
What you'll get
Reminders go out consistently — no more forgetting to follow up
Tiered escalation maintains client relationships while increasing urgency
Every reminder is logged, creating an audit trail for disputes
Frees up 2–4 hours per week that owners spend manually chasing payments
Common mistakes to avoid
Sending Tier 3 urgent emails to clients who are only 2 days late — damages relationships
Not filtering out invoices with partial payments, which overstates the amount owed
Running the workflow in a timezone that sends reminders at midnight local time for the client
Forgetting to add a flag for clients on payment plans to exclude them from automated reminders
Frequently asked questions
Do I need coding experience to set up this n8n automation?
No coding is required. This guide walks you through everything using n8n's built-in features and Zapier's visual interface. If you can follow a recipe, you can follow this guide.
How long does this automation take to set up?
Most users complete this setup in 30–60 minutes on their first try. Once set up, it runs completely automatically with zero ongoing effort.
What happens if the automation fails?
Zapier and Make both have error notifications and task history, so you'll know immediately if something goes wrong. We cover troubleshooting steps in the guide above.
Can I customize this automation for my specific business?
Absolutely. The guide includes notes on common customizations. Most automations have multiple variation points — timing, conditions, notification recipients, and more.