The finished build: all seven weeks in one 18-node workflow. It logs every invoice, sends a polite reminder at day 7 and a firmer one at day 14, stops the moment the invoice is paid, pings you if it's still open at day 30, and tells you when any step fails instead of quietly skipping that invoice. Import it, connect your sheet, email and Slack, and turn it on.
Still unpaid at day 30? It pings you in Slack. If the row reads Paid when it checks, nothing fires.
Before each email, the reminder re-reads that row and stops once it says Paid.
Any step fails on a real run? The failure is logged and you get a Slack message with a link to the run.
This is the whole build. Weeks 1 to 3 log every invoice and send two reminders, polite and then firm. Week 4 listens for the payment and skips any reminder still waiting once the row says Paid. Week 5 pings you in Slack when an invoice is still open at day 30. Week 6 adds an error branch, so a step that fails on a real run lands in an Error Log tab and in Slack with a link to the run, instead of that invoice dropping out quietly. The Sheets reads and updates retry three times before they count as failed. All 18 nodes are below.
Connects to a Google Sheets row or your invoicing tool. The moment a new invoice appears, the workflow wakes up.
A Google Sheets node appends every invoice to a tracking tab, Status Logged, before anything else happens — so nothing ever slips through unrecorded.
A Wait node holds the flow for exactly 7 days after the invoice was logged. No cron jobs, no external schedulers needed.
One check sits right before each email: the row is read again. If its Status isn't Logged any more (Paid, or anything you type by hand), that reminder never sends.
Sends a polite, professional payment reminder automatically. You never have to write or schedule the follow-up.
A second Wait node picks up where the first reminder left off. If nothing has been paid by day 14, the flow keeps going.
Same invoice, firmer wording. It names the due date, states the invoice is 14 days past due, and asks for a payment date — still professional, no chasing from you.
A Google Sheets update matches the row on Invoice Number and writes Second Notice to its Status column — so a glance at the tab tells you where every invoice stands.
A Webhook node your payment source calls when an invoice is paid: a Stripe invoice.paid event, or a QuickBooks or other automation posting the invoice number.
Checks the call carried an invoice number, then a Google Sheets update matches the row on Invoice Number and writes Paid to its Status column.
Holds the run 16 more days after the second notice. Seven plus seven plus sixteen is thirty — the node is named for the day it lands on, not the number inside it, so leave the value alone.
A Google Sheets read filtered to this invoice and Second Notice. If the listener already flipped the row to Paid, it finds nothing and the run stops right here — the same trick both Cancel Reminders nodes use.
A Slack message with the invoice number, client, amount and due date. Pick your channel once you connect the credential. No Slack? Swap it for an email to yourself, or a Telegram or SMS node — it's one node either way.
Starts whenever any step in the workflow fails on a real run: the hourly trigger, a resumed wait, or a payment webhook. It isn't wired to any node — it catches all of them. It does not fire on runs you start with Execute workflow, so test it with a real row.
Appends a row to an Error Log tab: when, which step, the error message, and a link to the failed run. The alert can't see the invoice's data, so open the link to see which invoice it was. If Sheets itself is down, it retries, then lets the Slack alert go out anyway.
A Slack message with the failed step, the error and the run link. It tells you — it doesn't fix it: that invoice's run has stopped, so re-run it or re-add the row. It can't catch a reminder your mail server accepted that bounces later, and during an outage you'll get one message per failed run.
No coding required. If you have an n8n account (self-hosted or cloud), you're ready to go.
Click the button above. You'll get an n8n workflow JSON file.
In your n8n canvas, click + → Import from File and select the JSON.
Point the trigger at your invoice tab, and every other Sheets node at one tracking tab with a Status column.
Change the Payment Received node's Path to your own random string (everyone who imports this starts with the same one), then copy its URL into Stripe (invoice.paid) or whatever automation knows when you're paid. Keep that URL private: it has no auth, so anyone who has it can mark an invoice paid (n8n's Header Auth option locks it down if your sender can add a header). Paid by hand? Just set the Status cell to Paid.
Connect a Slack credential on Ping Me and Alert Me and pick your channel on each. Don't use Slack? Swap those nodes for an email to yourself, or a Telegram or SMS node.
Add a tab called Error Log with the headers When, Failed Step, Error, Execution, and point Log the Failure at it. No workflow-settings change needed — a workflow with an Error Trigger uses itself as its error workflow.
Toggle the workflow on. The next invoice row triggers it automatically — no further action needed.
Seven Mondays, one step at a time, built in public on LinkedIn, Instagram, TikTok and Facebook. The build is done and the complete template is free above. Known limits, so nothing surprises you: the error branch covers steps that fail on a real run — it tells you, it doesn't retry the invoice for you. Two things it can't see: a reminder your mail server accepted that bounces later, and runs you start by hand. One edge case from Week 5 still stands: a payment recorded in the seconds between the day-14 check and the status write can be overwritten back to Second Notice, which lets the day-30 ping fire anyway.
If you'd rather have the full invoice chaser set up and running — connected to your tools, tested, handed over — that's what we do at Genesis Web Digital.