Nurho / automation engineering
Approach Process Workflows Writing About Calculator
See if we're a fit
Workflows

Invoice Chaser

Ep 03 · Google Sheets · Gmail

The average invoice sits unpaid for about three weeks. Not because customers refuse to pay, but because nobody enjoys chasing money.

Chasing money feels awkward, so it gets postponed. The invoice ages, your cash flow chokes, and you end up doing the stressing that your customer should be doing.

What it does

Every morning at nine, the workflow reads your invoice sheet. Anything three days overdue gets a friendly nudge with a payment link. Ten days, a firmer second reminder. Twenty days, a final polite note that flags the invoice for a phone call. Each email merges the real details, the invoice number, the amount, the due date, and sounds like you wrote it.

The tone escalation matters. A robot that sends the same nag on a loop trains people to ignore it. Three distinct messages, each slightly firmer, reads like a person who is paying attention.

How it works

A daily schedule reads the sheet and computes how overdue each unpaid invoice is. A stage guard makes sure no one gets the same reminder twice: the sheet tracks who was reminded, at which stage, and when. When a payment lands, you mark the row paid and the chasing stops. The whole system is one sheet and one workflow, and both are yours.

Setup

  1. Import the workflow file into your n8n instance.
  2. Copy the invoice sheet template (linked in the workflow's note) or map the columns to your existing one.
  3. Connect Gmail and adjust the three reminder templates to sound like you.
  4. Set your payment link so every reminder carries it.
  5. Run it once manually against a test row before switching on the daily schedule.

The template runs on n8n, any recent version, cloud or self-hosted. Every place that needs one of your accounts is marked with a note inside the workflow.

Get the workflow

The file arrives by email. No newsletter, no drip sequence: at most an occasional note when a workflow you grabbed gets an important fix. See privacy.

Rather have this running in your business without touching a single node? That is the actual job. Write to hello@nurho.net or start with the ROI calculator to see if it is even worth automating.

Nurho / automation engineering

Production-grade automation, built by an engineer. Helsinki-based, working with clients across the US, UK & Europe.

Nurho · Helsinki, Finland
hello@nurho.net

Site

  • Approach
  • Process
  • What it looks like
  • Live demo
  • FAQ
  • Free workflows
  • Writing
  • About
  • ROI calculator

Elsewhere

  • LinkedIn
  • GitHub
  • hello@nurho.net
  • Privacy policy
  • Terms of service
© 2026 Nurho · Helsinki, Finland Working with clients across the US, UK & Europe