# Unpaid invoice follow-up in n8n without sounding like collections

An unpaid invoice needs a three-step sequence that stops when they pay, and a last nudge you approve by hand. n8n can schedule and skip; you still hit send. This page is not a letter dump. Get Paid in 7 Days is the $19 cadence: Day 0 send, Day 3 nudge, Day 7 decision. Product /products/get-paid-in-7-days. Buy /buy/get-paid-in-7-days.

_Published 2026-05-06. Updated 2026-09-02._

Canonical HTML: https://buyebooks.store/guides/n8n-unpaid-invoice-follow-up
Markdown twin: https://buyebooks.store/guides/n8n-unpaid-invoice-follow-up.md

Late invoices are usually not malice. They are a client’s AP queue, a missed email, or a card that expired. Your job is to remind them on a schedule you would be willing to receive, stop immediately when they pay, and never let a workflow send a threat. n8n is good at the schedule and the stop. You still own the wording.

This sequence is three messages: a soft ping, a clearer reminder with the invoice attached or linked, and a last note you approve by hand. It is not a credit policy and it is not legal advice. If a client is genuinely in dispute, take it off the automation.

## Start from a source of truth

Pick one system that knows whether an invoice is open: Stripe, FreshBooks, QuickBooks, a sheet you actually update, or your accountant’s tool. Do not mix two sources. The workflow should query that system, not your memory.

Every night (or every weekday morning), list invoices whose due date has passed and whose status is open. Filter out anything you have marked “paused,” “in dispute,” or “write-off.” Include invoice number, amount, currency, due date, client name, and the email that should receive reminders — which is not always the person you Slack with.

## A boring three-step cadence

Day 3 after due: one short email. Subject with the invoice number. Body: the invoice is unpaid, here is the link, reply if the email is wrong. No apology essay. No “just bumping this.”

Day 7: same facts, plus a PDF or a clearer payment link, plus your usual payment methods. If you offer two methods, list both. Confusion delays payment more than tone does.

Day 14: do not auto-send. Create a draft and a task for you. The last message is where people get sharp, and sharpness does not belong in an unattended node. You might pick up the phone instead. The workflow’s job is to make sure day 14 does not pass in silence.

## The stop condition is the whole product

Before every send, re-fetch the invoice status. If it is paid, voided, or you marked it paused, skip and write a log row. Never trust a Wait node that started a week ago. Payment can arrive while the workflow is sleeping.

Store state in a sheet or a small table: invoice_id, last_step_sent, last_sent_at, status. The schedule job reads that table, not a pile of waiting executions. Waiting executions are how you get a day-7 email after you already marked something paid in the UI and forgot the workflow was still sitting there.

If your billing tool can fire a “invoice paid” webhook, use it to stamp the row immediately. The nightly job remains the backstop.

## Write the emails like a person with a job

Keep messages under 90 words. Use the client’s name and the project name. Put the amount and due date in the first three lines. Put the pay link on its own line. Close with your name, not a department.

Avoid: “per our records,” “further action,” “outstanding balance remains,” and anything that sounds like a bureau. Avoid humor about money. Avoid public CC lists. BCC yourself if you need a copy; do not CC the whole company on the client side.

If you want a model to draft the day-3 text, feed it your voice rules and the facts, then save the output as a template you edit once. After that, the template is enough. Generating a new letter every night is how you get a weird sentence into a money email.

## Build order in n8n

Workflow A — nightly scan: Schedule → fetch open overdue invoices → merge with state table → decide which step is due → send or create draft → update state. Workflow B — paid webhook: stamp state as paid and cancel any open task. Workflow C — error: email you if the fetch fails so a silent API outage does not look like “nobody owes me.”

Test with a fake invoice to your own address. Pay it between day 3 and day 7 and confirm day 7 never sends. Then test a missing pay link so you see the error path. Only then point it at real data, and start with one client you trust.

## What this will not do

It will not negotiate a payment plan. It will not decide who is in the wrong. It will not replace a conversation when a project went sideways. Those are you. The workflow exists so invoices you both agree on do not sit unpaid because you were busy shipping the next job.

If a large share of invoices go past day 14, the problem is probably scoping, deposits, or who you take on — not the reminder copy. Fix that in the sales conversation. Automation should not paper over a leaky intake.

Get Paid in 7 Days is the $19 cadence that owns the words and the days: Day 0 send, Day 3 nudge, Day 7 decision. Product https://buyebooks.store/products/get-paid-in-7-days. Checkout https://buyebooks.store/buy/get-paid-in-7-days. After Stripe, I email the PDF to the checkout address, usually within about an hour. You still hit send. This page is not a letter dump.

## FAQ

### How do I follow up on an unpaid invoice without sounding like collections?

Three messages: a short day-3 ping with the invoice number and pay link, a clearer day-7 reminder, and a day-14 note you approve by hand. Stop the moment it is paid. Keep the tone like a person with a job. Avoid “per our records,” “further action,” and anything that sounds like a bureau.

### Should n8n auto-send the last reminder?

No. Day 14 is a draft plus a task for you. Sharpness does not belong in an unattended node. A tool may draft. You still hit send. A workflow that auto-sends “work is paused until you pay” is a second incident.

### Is this a dump of invoice letters I can paste?

No. This page is the sequence: source of truth, cadence, stop-on-paid, human gate, build order. It is not a letter pack. Copy-ready invoice emails live in Get Paid in 7 Days, $19: https://buyebooks.store/products/get-paid-in-7-days. Buy: https://buyebooks.store/buy/get-paid-in-7-days.

### What is Get Paid in 7 Days?

A $19 PDF cadence: Day 0 send the invoice the day work ships, Day 3 nudge, Day 7 decide pause / plan / write-off. You still hit send. After Stripe, I email the PDF to the checkout address, usually within about an hour. Do not pay $29 for the starter and expect this PDF.

### Will this collect the money for me?

No. Clients pay on their AP calendar. You control the send, the follow-up, and whether you keep working. You do not control their cash. If a large share of invoices go past day 14, the leak is probably scoping, deposits, or who you take on — not the reminder copy.

### Do I need the $29 starter for this?

No. The calendar is the product. The canvas is optional. The $29 starter has unpaid-invoice plumbing. This page and Get Paid own the words and the days. Never send this title to the starter Payment Link.

## Get Paid in 7 Days — $19

- [Get Paid in 7 Days](https://buyebooks.store/products/get-paid-in-7-days) — $19. Buy: https://buyebooks.store/buy/get-paid-in-7-days

You still hit send. This page is not a letter dump. Do not pay $29 for the starter and expect this PDF.