Six n8n Workflows Every Sub-10-Person Business Should Be Running

Under 10 people is a tricky size for automation. You have enough volume that manual work hurts, but not enough budget to hire a full-time operations person. You're the operations person, on top of whatever else you do.

Most automation advice at this size assumes you have unlimited time to learn and configure tools. That's the wrong assumption. Here are the six n8n workflows I deploy most often for sub-10-person Canadian businesses, in the order I'd build them, with what they actually do and what they connect.

Why n8n specifically

For sub-10-person businesses, three things matter:

1. No per-task pricing. Zapier's per-task cost compounds fast at real volume. n8n is open source, run it on a $10/month VPS, run as many workflows as you want.
2. Self-hostable. Canadian businesses dealing with PIPEDA or industry-specific compliance often need data to stay on infrastructure they control. n8n self-hosted satisfies that.
3. Real conditional logic and error handling. Simpler tools (IFTTT, basic Zapier) handle "if X then Y" but break on real business flows that need branching, retries, and structured error handling. n8n was built for that.

The tradeoff is that n8n has a steeper learning curve than the simpler options. That's why my clients pay me to set it up — once the workflows are running, they don't really need to touch n8n itself except to add new flows.

Workflow 1: Lead capture to CRM with deduplication

What it does: every inbound lead — from your website form, your chatbot, your email inbox, your social DMs, your AI receptionist — gets normalized and written to the CRM as a single contact record. Duplicates (same email or phone) get merged.

Why it matters: most under-10 businesses have leads scattered across 4-7 channels, and the team spends hours every week copying them between systems or, worse, missing them entirely.

Nodes I use: webhook trigger or polling triggers per source, a Set node to normalize the field names, a CRM node (HubSpot, Pipedrive, Zoho, or RAS Flow) to upsert by email, and a Slack notification to alert the team on every new lead.

Estimated time saved: 4–8 hours/week for sales-heavy businesses.

Workflow 2: Calendar booking → confirmation + reminder + post-call follow-up

What it does: a new booking in Google Calendar, Calendly, or via the AI receptionist triggers a sequence — confirmation email immediately, SMS reminder 24 hours before, follow-up email or SMS 2 hours after the meeting ends.

Why it matters: no-show rates drop by 30-50% with proper reminders, and the team stops manually sending each one.

Nodes I use: calendar webhook, a few HTTP request nodes to send SMS via Twilio, email via SendGrid or your transactional email provider, with delay nodes for the timing.

Estimated time saved: 2–4 hours/week; plus the no-show reduction often pays for the entire setup in the first month.

Workflow 3: Invoice → reminder → escalation

What it does: a service completion or order trigger creates an invoice in Stripe / QuickBooks / Xero, sends it to the customer, and starts a follow-up sequence — friendly reminder at 7 days unpaid, firmer reminder at 14 days, owner notification at 21 days.

Why it matters: collections is one of the easiest places for under-10 businesses to leak revenue. Owners hate doing it manually, so they don't, and invoices age into uncollectable.

Nodes I use: trigger from whatever signals "service done" (a Slack reaction, a CRM stage change, a webhook from the operational tool), Stripe/QuickBooks node to create the invoice, and a Wait + Email sequence for follow-ups.

Estimated time saved: 3–5 hours/week, with revenue retention as the bigger effect.

Workflow 4: Document intake (OCR + LLM extraction + routing)

What it does: a document lands in a specific inbox or upload folder. n8n picks it up, OCR's the contents (Google Vision API or AWS Textract), passes the text to an LLM that extracts the structured fields you care about (invoice number, total, vendor, etc.), validates the data, and writes it into the right system. Humans only touch it on validation failures.

Why it matters: any business that deals with vendor invoices, receipts, intake forms, or contracts loses hours every week to manual data entry from documents.

Nodes I use: IMAP or Google Drive trigger, an HTTP request to the OCR API, an OpenAI node for extraction with a strict schema, an IF node for validation, and a routing node to the destination system.

Estimated time saved: 3–6 hours/week, depending on document volume.

Workflow 5: Weekly business digest

What it does: every Sunday night, n8n pulls data from your operational tools — Stripe revenue, CRM new leads, support tickets, calendar load — and assembles a single digest email. Owner reads it Monday morning over coffee, has full context on the business without digging.

Why it matters: under-10 owners run lean on time and tend to skip metrics review when it requires logging into 5 systems. A pre-assembled digest gets read; raw dashboards don't.

Nodes I use: Cron trigger, HTTP request nodes against each tool's API, a Function node to assemble the markdown, and an Email node to deliver.

Estimated time saved: 1–3 hours/week of manual reporting, plus the strategic benefit of an owner who stays informed.

Workflow 6: Customer review request automation

What it does: 3 days after a successful transaction or service completion, an SMS or email goes out asking the customer to leave a review on Google. If they click through and leave a review, log it. If they don't, send one polite reminder 7 days later.

Why it matters: Google reviews are one of the highest-leverage local SEO assets for service businesses. Most under-10 owners ask for reviews ad-hoc, miss most opportunities, and end up with 8 reviews when their competitor has 80.

Nodes I use: transaction-completion trigger, Twilio SMS node, conditional logic on whether the review was left (tracked via a webhook on the Google review API), and a follow-up branch.

Estimated time saved: less time, more revenue — review growth is one of the highest-leverage SEO moves available.

What this costs to build

For a sub-10-person Canadian SMB, I typically build all six workflows for ~$4,500–$6,500 total depending on integration complexity. Plus a $10/month VPS for self-hosted n8n. Plus the variable usage costs of whatever APIs the workflows hit (Twilio SMS, OpenAI tokens, OCR). Realistic monthly variable cost: $20–$100.

Standard timeline: 3–5 weeks for all six, sequential. We don't parallel-build because each workflow needs real testing in production before the team trusts it.

If your sub-10 business is leaking time to any of these patterns, book a call and I'll point at the two highest-leverage workflows for your specific setup. Or read more about workflow automation and the kinds of integrations we support out of the box.