Automate Client Invoice Follow-Up With Make.com (2026)
There’s a particular kind of dread that comes with chasing an unpaid invoice. You know the client. You like the client. But two weeks past the due date, you’re sitting there trying to figure out whether to send a firm email, a gentle nudge, or just pretend it’s not happening. It’s one of the most uncomfortable, time-consuming parts of running a service business — and it’s almost entirely automatable.
Make.com (formerly Integromat) is one of the most capable automation platforms available to small business owners, and invoice follow-up is one of its most practical use cases. Once your scenario is live, overdue invoices trigger reminders automatically, the timing is consistent, and you never have to think about it. This guide walks you through exactly how to build it — from connecting your tools to sending a multi-stage reminder sequence.
What You Need Before You Start
This workflow connects three components: your invoicing tool, Make.com, and your email or communication platform. Before you start building, confirm you have:
- A Make.com account — the free plan (1,000 operations/month) is enough for most solopreneurs
- An invoicing tool with a Make.com integration — QuickBooks, FreshBooks, Xero, Stripe, Wave, or Invoice Ninja all work
- A connected email account — Gmail, Outlook, or any SMTP-compatible email
- A Google Sheet or Airtable base (optional but recommended) — for logging follow-up activity so you have a record
If your invoicing tool isn’t directly integrated with Make.com, you can use a Google Sheets workaround: export your overdue invoices to a sheet and trigger the automation from there. It’s one extra step but works for any invoicing system.
Understanding the Workflow Logic
Before building anything in Make.com, it helps to map out what you’re automating. A typical invoice follow-up sequence looks like this:
- Trigger: An invoice becomes overdue (past due date, unpaid status)
- Day 1 overdue: Friendly first reminder — “Just checking in, your invoice is due”
- Day 7 overdue: More direct second reminder — “Following up on the unpaid balance”
- Day 14 overdue: Firm final notice — payment terms, next steps
- Log: Each reminder is recorded so you have a paper trail
In Make.com, this translates to a scheduled scenario that runs daily, checks for overdue invoices, evaluates how many days past due each one is, and routes to the appropriate email template. The branching logic is handled by Make’s Router module — no code required.
Step-by-Step: Building the Invoice Follow-Up Scenario
Step 1: Create a New Scenario in Make.com
Log into Make.com and click Create a new scenario. You’ll start with a blank canvas. Name it something specific — “Invoice Follow-Up Sequence” — so it’s easy to find when you come back to edit it.
Step 2: Add Your Trigger Module
Click the empty circle to add your first module. Search for your invoicing tool — let’s use QuickBooks Online as an example.
Select the trigger: Watch Invoices or Search Invoices. For a daily follow-up check, you’ll use a Scheduled trigger rather than a real-time webhook — this way the scenario runs once per day at a set time (9 AM is common) and checks for any overdue invoices at that moment.
Configure the filter:
- Status: Unpaid
- Due date: less than or equal to today’s date
This returns a list of every unpaid invoice whose due date has passed.
Step 3: Add a Router to Branch by Days Overdue
After your trigger module, add a Router module. This splits the flow into separate paths based on conditions — in this case, how many days past due the invoice is.
You’ll create three routes:
- Route 1: Due date = yesterday (1 day overdue) → first reminder
- Route 2: Due date = 7 days ago → second reminder
- Route 3: Due date = 14 days ago → final notice
In each route’s filter, use Make’s date functions to calculate the difference between today and the invoice due date. The formula looks like: {{dateDifference(now; invoice.dueDate; "days")}} — set it equal to 1, 7, or 14 for each respective route.
Step 4: Add Email Modules for Each Route
At the end of each Router route, add a Gmail (or Outlook) Send an Email module. Each one gets a different email template:
Route 1 — First reminder (friendly):
Subject: Quick note — Invoice #{{invoice.number}} is due
Hi {{client.name}}, just a friendly reminder that Invoice #{{invoice.number}} for {{invoice.amount}} was due on {{invoice.dueDate}}. If you’ve already sent payment, please disregard this message. Otherwise, here’s the payment link: [link]. Thanks!
Route 2 — Second reminder (direct):
Subject: Following up — Invoice #{{invoice.number}} (7 days overdue)
Hi {{client.name}}, I wanted to follow up on Invoice #{{invoice.number}} for {{invoice.amount}}, which was due on {{invoice.dueDate}}. Could you let me know when to expect payment? Payment link: [link].
Route 3 — Final notice (firm):
Subject: Final notice — Invoice #{{invoice.number}} now 14 days overdue
Hi {{client.name}}, this is a final reminder that Invoice #{{invoice.number}} for {{invoice.amount}} is now 14 days past due. Please arrange payment by [date] to avoid any interruption to ongoing work. Payment link: [link].
Use Make’s variable mapping to pull client name, invoice number, amount, and due date directly from your invoicing tool into each email template.
Step 5: Add a Logging Step (Highly Recommended)
After each email module, add a Google Sheets or Airtable module to log the reminder. Append a new row with: client name, invoice number, amount, reminder type (1st/2nd/Final), and timestamp.
This log is your paper trail if a payment dispute ever comes up. It also lets you see at a glance which clients are chronically late — useful information for future project terms. For more on building a comprehensive client tracking system, the guide to best Airtable automations for small business covers complementary workflows that pair well with this setup.
Step 6: Schedule and Activate
Set your scenario to run on a scheduled trigger — daily, at 9:00 AM. Click the clock icon in the scenario settings to configure this. Then toggle the scenario from Off to On.
From this point forward, every morning Make.com wakes up, checks your invoicing tool for overdue invoices, and sends the appropriate reminder to any client who hits the 1, 7, or 14-day threshold. You don’t have to think about it again.
How Make.com Compares to Other Invoice Automation Options
Make.com isn’t the only way to automate invoice follow-up. Here’s how your options stack up:
| Option | Best For | Cost | Setup Complexity | Customization |
|---|---|---|---|---|
| Make.com | Custom multi-step sequences | Free–$9/mo | Moderate | Very high |
| Zapier | Simple single-step reminders | Free–$29.99/mo | Easy | Moderate |
| Built-in invoicing tool reminders | Basic automated reminders | Included | Very easy | Low |
| Manual process | High-touch client relationships | Free | None | Total |
The built-in reminder feature in tools like FreshBooks or QuickBooks is worth enabling first — it handles basic follow-up with zero setup. Where Make.com earns its place is when you want branching logic (different messages at different overdue thresholds), cross-platform logging, or integration with other parts of your client workflow. If Zapier is already your automation platform, it can handle a simplified version of this — but Make’s visual scenario builder and more generous free plan make it the better choice for multi-step sequences. For a full comparison of the platforms, our best Zapier alternatives for small business breakdown covers the tradeoffs in detail.
Extending the Workflow: What Else You Can Automate Around Invoicing
Once your follow-up sequence is running, the same Make.com scenario can be extended with a few additional modules that save even more time:
- Auto-pause active projects — if an invoice goes 14+ days unpaid, trigger a task in ClickUp or Airtable to flag the project for review before continuing work
- Update your CRM or client tracker — push overdue invoice status into your client database so it’s visible in your weekly review
- Send yourself a summary digest — instead of checking your invoicing tool daily, have Make.com email you a morning summary of all open invoices and their status
- Trigger a contract review — if a client hits the final notice stage, automatically create a task in Notion or ClickUp to review your contract terms before further work
This invoice workflow fits naturally into a broader client operations system. If you’re building out the full stack, the client onboarding automation guide covers the front end of the client lifecycle — so from signed contract to first invoice is as automated as the payment follow-up side.
- Make.com’s Router module lets you build a multi-stage reminder sequence — different emails at 1, 7, and 14 days overdue — with no coding and on the free plan for most small businesses.
- Always test with Run once mode using your own email before activating on a live schedule — misconfigured date filters can send wrong-stage reminders to the wrong clients.
- Add a Google Sheets or Airtable logging step to every reminder path so you have a timestamped record of every follow-up sent — invaluable if a payment dispute ever comes up.
- Make.com beats both Zapier and built-in invoicing reminders for this use case because it handles branching logic and cross-platform logging in a single visual workflow.
- Extend the scenario with a VIP client exclusion filter so your most important relationships always get a personal touch rather than an automated nudge.
Frequently Asked Questions
Do I need a paid Make.com plan to automate invoice follow-up?
No — Make.com’s free plan includes 1,000 operations per month, which is more than enough for most solopreneurs and small service businesses running daily invoice checks. A scenario that processes 20 overdue invoices per day and sends emails uses roughly 60–100 operations per day, well within the free tier. You’d only need a paid plan (starting at $9/month) if you’re running many concurrent scenarios or processing very high invoice volumes.
What invoicing tools work with Make.com for this workflow?
Make.com has native integrations with QuickBooks Online, FreshBooks, Xero, Stripe, Wave, Zoho Invoice, and Invoice Ninja, among others. If your tool isn’t directly supported, you can use its API via Make’s HTTP module, or export overdue invoices to Google Sheets and trigger the scenario from there. The Google Sheets workaround adds one manual step but is reliable for any invoicing system.
Will automated invoice reminders feel impersonal to my clients?
Only if they’re written poorly. A well-written first reminder that uses the client’s name, the specific invoice number, and a friendly tone reads as professional rather than robotic. The key is avoiding generic language — write your templates as you would write a personal email, just once, and the automation delivers that same quality every time. For highest-value clients, add a VIP exclusion filter and handle those manually.
Can I use Make.com to stop reminders automatically once an invoice is paid?
Yes — this is an important part of the scenario. In each Router route, add a filter that checks the invoice status before sending: if status equals “Paid,” skip the email module and route to a “do nothing” path. Most invoicing integrations return live invoice status, so the check happens in real time each time the scenario runs. This prevents the embarrassing situation of sending a reminder to a client who paid yesterday.
How is this different from just enabling automatic reminders inside my invoicing tool?
Built-in reminders are fine for basic follow-up — if your invoicing tool has them, enable them. Make.com earns its place when you need things the built-in system can’t do: different email content at different overdue thresholds, logging to an external spreadsheet or database, pausing projects in your project management tool, excluding specific clients, or integrating the follow-up into a broader client operations workflow. If you’re already automating other parts of your business in Make.com — like client reporting or email workflows — adding invoice follow-up to the same platform keeps everything consolidated and visible in one place.
2 Comments