Your Handy AI Guide
Free Guide · 13 min read

5 n8n Automations Every Small Business Should Run

The five builds I set up most for real clients: lead capture, review requests, invoice reminders, a weekly report, and inbox triage. Each one has a human approval step.

Category: Automation13 min readPublished October 2026
yourhandyaiguide.com
Guides/Automation
Free Guide · From real client work

5 n8n Automations Every Small Business Should Run

The five builds I set up most for real clients: lead capture, review requests, invoice reminders, a weekly report, and inbox triage. Each one has a human approval step.

13 min read Published October 2026 Category: Automation

I've built dozens of automations for small businesses. Almost all of them fall into five categories. That's not a coincidence. Most of what eats a small business owner's week isn't hard work, it's repetitive work: someone fills out a form and needs a fast reply, a job wraps up and nobody asks for a review, an invoice slips past due and nobody chases it.

None of these need a developer. Each one is a trigger that watches for an event, a few steps that do something with it, and a person who approves anything before it leaves your building. I build these in n8n (say it "n eight n"), which is the platform I use for client work.

Below are the five I build most, with the trigger, the steps, the approval point and the thing most likely to go wrong. Build one this week. Don't try to build all five at once.

Before you build anything: four n8n words

If you've never opened n8n, four words make everything below make sense. Skip this section if you've built a workflow before.

  • Workflow: the whole automation. One trigger, then a chain of steps. Think of it as one recipe.
  • Node: one step in that chain. Each node is a box on a canvas that does one thing: receive a form, read a sheet, ask an AI to write, send an email.
  • Execution: one full run of a workflow, start to finish. n8n counts runs, not individual steps.
  • Test run: running the workflow on purpose with sample data, so you can click any node and see what went in and what came out.

You can try n8n Cloud on a free trial with no card, so you can build your first workflow before you decide anything. If someone technical helps you, they can also self-host the free Community Edition on their own server. For most owners, start on the trial. Plans and limits change, so check n8n's pricing page for the current terms instead of trusting a number in a guide.

Run it safely: the rule for every build below

An automation that runs while you sleep has to be safe to run while you sleep. Every build in this guide follows the same three-step rule, and it's the part people skip.

  1. Read first. The automation only reads and collects. It changes nothing in the real world yet.
  2. Draft second. Anything that would go to a customer lands as a draft or in an approval list. It does not send.
  3. A human says yes third. You read it and press send. Only after you've approved hundreds of drafts without editing them should you even consider letting one send on its own.

Automation 1: New lead to record to instant alert

This is the first one I build for almost every client, because it fixes the most expensive problem a small business has: a lead comes in and nobody responds for six hours. Speed to lead is the biggest lever most businesses never pull.

What it does

Someone fills in your website form. Within a minute, you get a message on your phone with their name, contact details and what they asked. The lead is also saved to your CRM or a leads sheet, and a drafted reply waits in your drafts folder.

The build

  1. Trigger: a Form Trigger node (or a Webhook node if your website form can send data). Add fields for name, phone, email and message.
  2. Save it: a node that adds a row to your leads sheet or creates a contact in your CRM. If you aren't sure which CRM node to pick, ask your builder.
  3. Draft a reply: an AI node connected to your Claude account that writes a short, friendly reply using the lead's name and message.
  4. Park the draft: an email node set to create a draft, not send.
  5. Alert you: a message node that texts or emails you the details, so you can decide who replies.
Prompt for the AI node
Write a short, friendly reply to this new lead for [BUSINESS NAME], a [WHAT YOU DO].

Lead name: [NAME]
Their message: [MESSAGE]

Rules:
- Under 90 words, plain language, no hype.
- Thank them by first name and answer only what they asked.
- Ask one clarifying question.
- Never promise a price, a date or availability.
- Sign off as [YOUR NAME].
In n8n, the bracketed fields become values dragged in from the trigger node.

What goes wrong: your form fields get renamed and the alert shows blanks, or the alert goes to an inbox nobody reads. Submit a fake lead after every change to your form.

Automation 2: Job done to review request

Reviews are free marketing that most businesses never ask for. The reason is simple: asking takes a minute, and nobody has a spare minute. This automation takes the minute off your plate.

What it does

When you mark a job complete in your scheduling tool or sheet, the workflow waits a day, drafts a short thank-you with your review link, and puts it in an approval list. You glance at each one and approve.

The build

  1. Trigger: a node that watches your scheduling tool or a sheet for a job marked complete.
  2. Wait: a Wait node set to one day, so the message doesn't land while the crew is still cleaning up.
  3. Check the list: a lookup against a column that records who was already asked. Stop here if they were.
  4. Draft: an AI node that writes the thank-you with your review link.
  5. Approve: save it as a draft or add it to an approval list. After you send, the workflow writes today's date in the "asked" column.
Prompt for the AI node
Write a short review request for a customer of my [TYPE OF BUSINESS].

Customer first name: [NAME]
Job they had done: [JOB]
My business name: [NAME]
Review link: [LINK]

Keep it under 60 words, warm and plain, with one clear ask. Do not offer anything in exchange for the review. Do not guess details I did not give you.

Automation 3: Past-due invoice to polite reminder

Chasing invoices is the task owners avoid longest and regret most. A polite reminder, sent on time, gets paid more often than an awkward one sent a month late.

What it does

Every morning, the workflow checks your invoice list for anything past due that hasn't had a reminder. It drafts a short, polite message for each and puts them in a review list for you.

The build

  1. Trigger: a Schedule Trigger node set to a time each morning.
  2. Read: a node that reads your invoice sheet or accounting tool.
  3. Filter: a node that keeps only invoices past due with no reminder in the last seven days.
  4. Draft: an AI node that writes a polite reminder with the amount and how to pay.
  5. Approve: drafts go to your review list. You read each one, send it, and the workflow stamps the "last reminded" date.
Prompt for the AI node
Write a polite payment reminder for [BUSINESS NAME].

Customer first name: [NAME]
Invoice number: [NUMBER]
Amount: [AMOUNT]
Due date: [DATE]
How to pay: [PAYMENT LINK OR INSTRUCTIONS]

Tone: friendly, assuming it slipped their mind. Under 70 words. No threats, no late-fee mentions, no guessing about why it's unpaid.

What goes wrong: an invoice was paid but the sheet wasn't updated, so you remind a customer who already paid. That's why you read every draft, and why the "last reminded" column exists, so one invoice never gets chased daily.

Automation 4: Monday morning report

Most owners can't say how last week went without opening four tabs. This automation puts the answer in your inbox before you've had your coffee.

What it does

Every Monday morning, the workflow gathers last week's numbers from the places you keep them (new leads, jobs completed, invoices sent) and asks an AI to turn them into five plain lines and one question to think about. It sends the note to you and only you.

The build

  1. Trigger: a Schedule Trigger node set to Monday at 8 a.m.
  2. Gather: one read node per source: your leads sheet, your job list, your invoice list.
  3. Combine: a node that merges the three into one block of numbers.
  4. Summarize: an AI node that writes the note.
  5. Send to yourself: an email or message node pointed at your own address.
Prompt for the AI node
Here are last week's numbers for my [TYPE OF BUSINESS]:

[PASTE THE NUMBERS]

Write five plain lines on how the week went, then one question I should think about this week. Use only the numbers above. If a number looks odd or a source is missing, say so instead of guessing.

What goes wrong: a source sheet changes shape and the numbers come out wrong while looking confident. For the first month, check one number against the real source each week.

Automation 5: Inbox triage and FAQ draft

Half of what lands in a small business inbox is the same dozen questions. Hours, service area, how to book, what's included. This automation drafts the answer so you only edit and send.

What it does

When a new customer email arrives, the workflow reads it, checks it against a short FAQ document you wrote, and drafts a reply that uses only that document. If the question isn't covered, the draft says so and flags the email for you.

The build

  1. Trigger: an email trigger node watching your support or info inbox.
  2. Classify: an AI node that labels the email: question, booking, complaint, or other.
  3. Route: complaints and "other" skip the draft and go straight to you with a flag. Questions and bookings continue.
  4. Draft: an AI node that writes a reply from your FAQ document only.
  5. Park the draft: an email node set to create a draft in your drafts folder, never to send.
Prompt for the AI node
You draft email replies for [BUSINESS NAME]. Use ONLY the FAQ below to answer. If the question is not covered by the FAQ, write "Not covered in FAQ: needs a human" and nothing else.

FAQ:
[PASTE YOUR FAQ]

Customer email:
[EMAIL TEXT]

Keep the reply under 100 words, friendly and plain. Never invent a price, an hour or a policy.

What goes wrong: the FAQ is out of date and the draft quotes an old price. Keep the document current, and don't let this one send on its own until you've read hundreds of its drafts.

When one breaks: set up an error alert once

Every automation breaks eventually. A password expires, a form changes, a sheet gets renamed. The danger isn't the break. It's the silence. You assume the lead alert is working for three weeks while it quietly isn't.

n8n has a built-in answer. You create one extra workflow that starts with an Error Trigger node. Whenever any of your other workflows fails, the Error Trigger fires, and you attach a message node that emails or texts you the workflow's name and what went wrong. Then you point your other workflows at it in their settings. Build it once, and every future automation inherits it.

One legacy note: if you already run something like these on Make.com, the logic carries over to n8n step for step, but I build every new one in n8n.

Which one to build first

If your biggest pain is...BuildWhy first
Slow replies to new leadsAutomation 1: lead alertDirect line to revenue, and the safest build because it only tells you
Too few reviewsAutomation 2: review requestEasy win, and the approval step protects you from asking an unhappy customer
Late paymentsAutomation 3: invoice reminderBrings cash in sooner, but needs a clean invoice sheet first
Never knowing how the week wentAutomation 4: Monday reportRead-only, so nothing can go wrong in front of a customer
A swamped inboxAutomation 5: inbox triageBiggest time saver, but build it last because it needs a good FAQ

Pick one. Get it solid. Run it for a month before you think about a second.

Where to go next

This guide gives you the five recipes. If you want the full walkthrough, with your first workflow built step by step, the approval routine explained, and each of these five built out with copy-paste prompts and a testing checklist, that lives in Your Handy AI Guide for Small Business.

Key takeaways

  • Five automations cover most of what a small business automates: lead alert, review request, invoice reminder, Monday report, inbox triage.
  • Every build follows one rule: read first, draft second, a human says yes third. Nothing customer-facing sends on its own.
  • Test with fake records, never real customers, and turn a workflow on only after a clean test run.
  • Build one error-alert workflow with an Error Trigger node so a broken automation tells you instead of failing quietly.
  • Build one automation, run it for a month, and give it an owner who checks it weekly before you add a second.

One more thing

Want guides like this in your inbox?

New guides drop every couple weeks. No spam, just practical AI from someone actually building it.

→ Keep going

What's next?

Three ways to go deeper. Scan the QR or hit the link. Both work.

Join the Community

Free community of small business owners and operators actually using AI.

Community QR
yourhandyaiguide.com/go/community

Work with Dylan

Custom AI builds and automations for your business. Direct line, no funnel.

Contact QR
yourhandyaiguide.com/contact

Get More Guides

The newsletter. Practical AI in your inbox every couple weeks. No spam.

Newsletter QR
yourhandyaiguide.substack.com
Your Handy AI Guide · A HandyCo brand · © 2026 yourhandyaiguide.com