n8n workflow automation: five workflows every small business needs

TL;DR — The automations that pay off for a small business are boring: route the lead, chase the invoice, ask for the review, welcome the new client, ping the team when something breaks. Build them in n8n (self-hostable, no per-step pricing), make each one idempotent and retry-safe, start with the single workflow that wastes the most of your week, and measure the hours you get back.

Most “automate your business” advice points at flashy AI agents and 40-node Rube Goldberg machines. That’s not where the time goes. The time goes to the same five chores, done by hand, every week, by someone whose hourly rate you’d rather spend elsewhere. n8n — an open-source workflow tool you can self-host — is purpose-built for exactly these chores: it talks to your CRM, your inbox, your invoicing tool and Slack, and it doesn’t bill you per execution.

Here are the five that earn their keep first.

The five workflows

1. Lead routing into your CRM

Every form submission, inbox query, or booking should land in your CRM within seconds — tagged, assigned, and never lost in an inbox. A webhook or email trigger fires, n8n normalizes the fields, dedupes against existing contacts, and creates or updates the record, then notifies the right person. This is the highest-leverage one because a lead that sits unanswered for an hour is mostly a lost lead.

2. Invoice follow-up and dunning

Unpaid invoices don’t chase themselves, and you don’t want to be the person sending the third awkward reminder. A scheduled workflow reads open invoices from your billing tool, checks how many days they’re overdue, and sends a polite, escalating sequence — friendly nudge at day 3, firmer note at day 14, a heads-up to you at day 30. It stops the moment the invoice is marked paid.

3. Review and testimonial requests

The best time to ask for a review is right after you’ve delivered something good. Trigger on a “project completed” or “order delivered” event, wait a sensible delay, then send a single, personal request with a direct link. Done consistently, this is the difference between a handful of reviews a year and a steady stream — without anyone remembering to ask.

4. Client onboarding and welcome sequences

The first week sets the tone. When a deal closes or a client signs, kick off a sequence: send the welcome email, create the project folder, schedule the kickoff, share the intake form, and add them to the right lists. The client feels organized; you skip the checklist you keep forgetting half of.

5. Internal alerts and reporting

You shouldn’t find out about a failed payment, a stuck form, or a sold-out service from an angry customer. A monitoring workflow watches the things that matter and posts to Slack or email when a threshold trips — plus a tidy Monday-morning digest of last week’s numbers, so the dashboard comes to you instead of the other way around.

Automation isn’t about removing people from the work. It’s about removing the work that shouldn’t need a person.

Build them so they don’t betray you

A flaky automation is worse than no automation, because you stop trusting it and start double-checking it by hand — now you’re doing both jobs. Two basics keep them honest:

Idempotency. Running the same workflow twice should not create two contacts, send two invoices, or fire two emails. Key your actions on a stable ID (the invoice number, the lead’s email) and check-before-create. Webhooks will fire twice eventually; design for it.

Retries with backoff. External APIs go down, rate-limit, and time out. Configure n8n’s per-node retry settings, fail loudly to a Slack channel when something genuinely can’t recover, and never let a single hiccup silently swallow a lead.

Add a dead-simple log — even a row in a spreadsheet or a database table per run — so when something looks off you can answer “did it run, and what did it do?” in ten seconds.

Where to start

Pick the one workflow that wastes the most of your week right now — for most small businesses that’s lead routing or invoice follow-up — and build only that. Wire it, run it idempotently, watch it for a week. Then write down the number: hours saved per week. That number is what tells you which of the remaining four to build next, and it’s the only honest way to know the automation is actually working for you instead of becoming one more thing to maintain.

Start with one. Measure the time it gives back. Then add the next.