Home › Guides

9 n8n workflows for small business, and what goes wrong with each

Nine practical n8n workflows that suit most small businesses: what each one does, the nodes it uses, and what tends to go wrong. About 8 minutes to read.

n8n is a workflow automation tool you can run on n8n's own cloud or host yourself. It connects apps like Gmail, Google Sheets, Google Calendar, Slack, Xero and QuickBooks, and it lets you add a small Code step when the built-in nodes aren't enough. For a small business that makes it a good fit for the dull, rules-based admin that eats a few hours each week.

Below are nine workflows that suit most service businesses, trades, studios, clinics and small online shops. Each one uses common nodes, and each comes with the pitfalls worth knowing before you switch it on. Check n8n's current pricing and plan limits on its site before choosing cloud or self-hosting, since they change.

Before you build anything

• Test with dummy data. Send everything to your own address first.
• Keep a human in the loop for anything that moves money, contacts customers in bulk, or sends AI-written text.
• Set the workflow time zone to your business time zone in the workflow settings. Many reminder bugs are really time-zone bugs.
• Check sending limits. Gmail and Google Workspace accounts have daily sending caps, and anti-spam laws apply to commercial email.

1. Overdue invoice reminders

Nodes: Schedule Trigger (weekdays 9:00) → Google Sheets (get rows) → Code (keep unpaid, overdue, not reminded in 7 days) → Gmail (send) → Google Sheets (update "last reminder").

Watch out for: a stale "status" column, which means paid clients get chased. If you use Xero or QuickBooks, read invoices from there instead of a sheet. Leave final notices and stopping supply to a human.

2. Website enquiry capture, auto-reply and alert

Nodes: n8n Form Trigger or Webhook → Google Sheets (append) → Gmail (acknowledge the enquirer) → Gmail or Slack (alert the owner).

Watch out for: spam submissions (add a honeypot field), and promising a callback time you can't keep. The main benefit is often faster replies rather than minutes saved, so measure time-to-first-reply before and after.

3. Appointment reminders 24 hours ahead

Nodes: Schedule Trigger (hourly) → Google Calendar (events starting 24–25 hours from now) → Gmail (reminder with time, place or link, and how to reschedule).

Watch out for: internal meetings. Only email attendees outside your own domain, or use a dedicated booking calendar. The one-hour window means each event is caught once. SMS needs a paid provider.

4. Shared inbox triage with AI labels and draft replies

Nodes: Gmail Trigger → AI step (n8n's AI nodes or an HTTP Request to your provider) with a fixed instruction to return one label from a short list → Gmail (add label) → Gmail (create draft).

Watch out for: auto-sending. Save AI replies as drafts for a person to review. Check your AI provider's data terms before sending customer emails to it.

5. Weekly KPI digest

Nodes: Schedule Trigger (Monday 7:30) → Google Sheets (one row per week) → Code (totals and week-on-week change) → Gmail (short digest).

Watch out for: too many numbers. Pick three to six that drive decisions, such as sales, enquiries, jobs completed and cash received. Someone must own keeping the sheet up to date.

6. Review request after a completed job

Nodes: Schedule Trigger (daily) → Google Sheets (jobs completed yesterday, no request sent) → Gmail (thank-you with review link) → Google Sheets (mark as requested).

Watch out for: review gating. Google's policies prohibit selectively asking only happy customers and offering incentives for reviews. Ask everyone the same way, once.

7. Supplier bills to a folder and a log

Nodes: Gmail Trigger on a bills@ address (download attachments) → Google Drive (upload to "Bills to process") → Google Sheets (log sender, date, file link).

Watch out for: logos and T&C attachments creating junk files. Filter to PDFs. Also check whether your accounting software already has a bill-forwarding email address, which may make this unnecessary. Payment approval stays with a human.

8. New client onboarding pack

Nodes: n8n Form Trigger (internal "new client" form) → Google Drive (create client folder) → Gmail (welcome email with next steps) → Google Sheets (client list).

Watch out for: folder sharing. Keep new folders restricted until you've checked permissions. Keep the welcome text in one place so it doesn't drift.

9. Low-stock alert

Nodes: Schedule Trigger (daily 8:00) → Google Sheets (SKU, on hand, reorder level) → Code (on hand ≤ reorder level) → Gmail (one reorder list).

Watch out for: stock numbers that aren't updated when items move. This works best when stock comes from your POS or e-commerce platform. Don't auto-order until the numbers have been reliable for months.

Which one first?

Don't build all nine. Pick the one that scores best on four questions:

• How often does it run?
• Are the rules clear enough to write on one page?
• Are the inputs already digital and consistent?
• What's the worst thing that happens if it misfires?

For many businesses that's invoice reminders or enquiry auto-replies. Run it for two weeks, check executions daily, and fix what breaks before adding the next. Our guide on what to automate first covers the scoring in more detail.

Importing templates safely

If you start from someone else's JSON workflow, use Workflows → Import from File. Then:

1. Connect your own credentials.
2. Replace every placeholder value, such as sheet IDs, emails and labels.
3. Read every Code node so you know what it does.
4. Run it manually with test data before activating.

Never paste API keys into a workflow you plan to share.

Want these ready to import?

The Spare Afternoon AI Automation Audit Kit includes importable n8n starting templates for all nine workflows above. It also has written recipes with the matching Make modules, and a workbook to score which ones are worth doing in your business.