n8n Build of the Week — Complete

Free n8n Invoice Chaser
Complete Template

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.

Download the Complete Template n8n workflow JSON · free · no email required · earlier steps: Week 1 · Week 2 · Week 3 · Week 4 · Week 5 · Week 6
What's inside

Seven weeks, one workflow that chases its own invoices.

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.

Node 01

Invoice Trigger

Connects to a Google Sheets row or your invoicing tool. The moment a new invoice appears, the workflow wakes up.

Node 02

Invoice Log

A Google Sheets node appends every invoice to a tracking tab, Status Logged, before anything else happens — so nothing ever slips through unrecorded.

Node 03

7-Day Wait

A Wait node holds the flow for exactly 7 days after the invoice was logged. No cron jobs, no external schedulers needed.

Nodes 04 & 07

Cancel Reminders

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.

Node 05

Email Reminder

Sends a polite, professional payment reminder automatically. You never have to write or schedule the follow-up.

Node 06

7 More Days

A second Wait node picks up where the first reminder left off. If nothing has been paid by day 14, the flow keeps going.

Node 08

Second Notice

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.

Node 09

Status Update

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.

Node 10

Payment Received

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.

Nodes 11–12

Mark as Paid

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.

Node 13

Wait to Day 30

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.

Node 14

Still Unpaid at 30?

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.

Node 15

Ping Me

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.

Node 16

Error Trigger

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.

Node 17

Log the Failure

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.

Node 18

Alert Me

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.

Getting started

Import and run in seven steps.

No coding required. If you have an n8n account (self-hosted or cloud), you're ready to go.

1. Download the JSON

Click the button above. You'll get an n8n workflow JSON file.

2. Import into n8n

In your n8n canvas, click + → Import from File and select the JSON.

3. Connect your sheets

Point the trigger at your invoice tab, and every other Sheets node at one tracking tab with a Status column.

4. Connect the listener

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.

5. Point the alerts at you

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.

6. Add the Error Log tab

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.

7. Activate

Toggle the workflow on. The next invoice row triggers it automatically — no further action needed.

The full build

7 weeks. One complete invoice chaser.

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.

01
The base template Invoice trigger → 7-day wait → email reminder. The 3-node foundation.
Week 1 · Done
02
Never lose track — log every invoice A Sheets node auto-logs every invoice before the first reminder fires.
Week 2 · Done
03
Escalating reminders — gentle first, firmer second Two-touch escalation: friendly at day 7, firmer at day 14. Status flips to Second Notice automatically.
Week 3 · Done
04
Auto-close when paid — the payment listener Mark an invoice Paid (from Stripe, QuickBooks, or the sheet) and every reminder still waiting for it is skipped.
Week 4 · Done
05
Know the moment something is overdue — owner alert Still unpaid 30 days after it was logged? A Slack message (or a text) lands in front of you instead of the invoice going quiet.
Week 5 · Done
06
Make it bulletproof — error handling An error branch logs any failed step and pings you in Slack, instead of an invoice silently dropping out.
Week 6 · Done
07
The finished build — and it's yours ← you are here All six steps in one 18-node workflow, free. Download it above, or comment INVOICE on the post and the link lands in your DMs.
Week 7 · Live

Want this built for your business?

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.