A working library to get started fast
When a small business owner discovers n8n, the first question is never technical: “In practice, what can I automate in my company?” This page gives the operational answer with 12 use cases deployed in small businesses in 2024-2026, grouped by department (sales, finance, HR, operations, marketing, support), each with the exact trigger, the workflow steps, the tools involved, the monthly hours saved and the complexity level.
These 12 workflows cover 70 to 80 percent of the typical needs of a B2B or e-commerce small business with 20 to 100 employees. They serve as the starting point for the prioritized top 10/15 in phase 1 (process mapping). Most can be built in 1 to 3 weeks by a trained no-code lead; some need occasional technical help on specific integrations.
This article is part of our series on no-code automation for businesses. To choose the platform before building these workflows, see our n8n vs Make vs Zapier 2026 comparison. For a structured deployment method, read our 6-phase implementation guide.
Overview: the 12 use cases by department
The workflows are organized by business function to make prioritization easier. The “Complexity” column uses a simple scale: S (simple, 1-3 days), I (intermediate, 1-2 weeks), A (advanced, 2-4 weeks with technical support).
| No. | Workflow | Department | Savings (hrs/month) | Complexity |
|---|---|---|---|---|
| 01 | CRM-to-accounting sync | Sales / Finance | 10-25 | I |
| 02 | AI lead qualification | Sales / Marketing | 8-18 | A |
| 03 | Automated overdue-invoice reminders | Finance | 5-12 | S |
| 04 | New-hire onboarding | HR / IT | 3-8 / hire | I |
| 05 | E-commerce–ERP inventory sync | Operations | 15-40 | A |
| 06 | Automatic quote generation | Sales | 8-20 | I |
| 07 | Automated competitive monitoring | Marketing / CEO | 5-10 | I |
| 08 | Weekly executive report | Leadership | 4-10 | I |
| 09 | Support ticket routing and SLAs | Support / IT | 12-30 | I |
| 10 | Multi-network social publishing | Marketing | 3-8 | S |
| 11 | Automatic document filing | Sales admin / Finance | 5-12 | S |
| 12 | Automated post-delivery NPS | Marketing / CS | 2-6 | S |
Combined across the 12 active workflows, the monthly time savings observed in small businesses range from 80 to 200 hours, the equivalent of 0.5 to 1.2 FTE freed up for higher-value work. Payback typically lands between 4 and 9 months, depending on the reference salary cost and the platform cost (see our automation cost and ROI analysis).
Sync the CRM with accounting when a deal is won
Department: Sales / Finance. Savings: 10 to 25 hours per month. Complexity: Intermediate. Tools: HubSpot / Pipedrive / Salesforce + Sage / Pennylane / QuickBooks.
Trigger
A deal moves to “won” in the CRM, or an opportunity is marked “closed-won” in Salesforce.
n8n workflow steps
- Webhook or CRM polling every 5 minutes to detect won deals
- Check that the customer does not already exist in the accounting tool (search by company registration number or email)
- If new: create the customer record (legal name, registration number, address, email)
- Create the invoice with the deal’s line items (products, quantities, prices excl. VAT, VAT)
- Automatically email the invoice to the customer with the PDF attached
- Slack notification to the sales rep with a link to the new invoice
- Update the deal in the CRM with the invoice number for traceability
Measured savings and benefits
Saves 30 to 90 minutes per deal (looking up, re-keying, checking). For a small business closing 30 to 80 deals a month, monthly savings range from 10 to 25 hours. Side benefits: reliable data between sales and finance (no more re-keying errors), faster invoicing and therefore faster cash (DSO down 3 to 7 days), and full deal-to-invoice traceability for audits.
Implementation tip
Start in “create draft” mode rather than sending directly to the customer for the first 4 weeks: an accountant approves each invoice before it goes out, until you have confirmed the CRM data is reliable. Once quality is confirmed, switch to auto-send with a safeguard rule (manual approval if the amount exceeds €10k).
Qualify and route inbound leads with AI scoring
Department: Sales / Marketing. Savings: 8 to 18 hours per month. Complexity: Advanced. Tools: Web forms + GPT-4o / Claude API + CRM + Slack.
Trigger
A contact form is submitted on the website (demo request, sales inquiry, white paper download).
n8n workflow steps
- Inbound form webhook with prospect data (name, email, company, message)
- Enrichment through an external API (Dropcontact, Apollo) to retrieve company ID, industry, headcount, revenue
- Call to an OpenAI or Anthropic node with a qualification prompt (ICP fit, urgency, likely budget)
- Retrieve the score (1-100) and the category (Hot / Warm / Cold / Disqualified)
- Create or update the lead record in the CRM with score and tags
- If Hot: Slack notification to the sales rep with enriched context and an immediate call to action
- If Warm: add to an automated email nurturing sequence
- If Cold / Disqualified: send a generic automated email with no sales involvement
Measured savings and benefits
For a small business receiving 80 to 250 leads a month, this saves 5 to 12 minutes per lead on manual qualification and routing, or 8 to 18 hours a month. Side benefits: response time to Hot leads cut by a factor of 5 (from 4-8 hours to under an hour), conversion to qualified meetings up 25 to 40 percent thanks to prioritization, and sales reps freed from unqualified leads.
Implementation tip
Document your ICP (Ideal Customer Profile) precisely in the AI prompt before anything else: target industries, company size, buying signals. Test the scoring on 200 historical leads with known real outcomes to calibrate the prompt before going live. Poorly calibrated scoring disqualifies good prospects and costs you revenue.
Automate tiered reminders for unpaid invoices
Department: Finance. Savings: 5 to 12 hours per month. Complexity: Simple. Tools: Accounting tool + email + SMS API + Slack.
Trigger
A daily cron job at 8:00 a.m. queries the accounting tool and flags invoices unpaid past their due date.
n8n workflow steps
- Daily cron job querying the accounting API to retrieve all unpaid invoices
- Calculate the number of days overdue for each invoice
- Conditional branching by overdue tier (D+3, D+10, D+20, D+30, D+45)
- D+3: polite automated reminder email with the invoice PDF attached
- D+10: firmer follow-up email mentioning the delay and accounting contact details
- D+20: email + text message to the signatory offering a payment plan
- D+30: Slack notification to the CEO and the account’s sales rep for a manual call
- D+45: automatic generation of a formal notice of default and a legal alert
- Update the customer record in the CRM with the reminder history
Measured savings and benefits
For a small business with 100 to 300 open invoices, this saves 5 to 12 hours a month (no more weekly manual follow-up). Main benefit: DSO (Days Sales Outstanding) down 5 to 15 days, which typically frees up €30k to €150k of additional cash over the year. Side benefits: full reminder history for collections, and depersonalized reminders (less friction between people).
Implementation tip
Start with email templates signed by a person (the CFO by name), not an anonymous “Accounting”. Always attach the invoice PDF to the first reminder to remove the “I never got it” excuse. Keep an exclusion list (key strategic accounts, customers in active negotiation) to handle manually.
Orchestrate new-hire onboarding
Department: HR / IT. Savings: 3 to 8 hours per hire. Complexity: Intermediate. Tools: HR tool + Microsoft 365 / Google Workspace + Slack / Teams + business apps.
Trigger
A new employee is created in the HR tool with a start date (Lucca, PayFit, Personio, BambooHR).
n8n workflow steps
- HR webhook fired when the employee record is created
- D-7 before arrival: create the Microsoft 365 or Google Workspace account with a temporary password
- D-7: HR emails a welcome note with portal access and the week-1 schedule
- D-3: create Slack / Teams accounts and add to department channels
- D-3: automatically generate the access badge and notify the facilities manager
- D-2: automatically order equipment (laptop, headset) from the supplier
- Day 1: internal welcome email with photo and introduction to the rest of the team on Slack
- D+30: automatically send a 30-day experience survey
- D+90: reminder to the manager for the end-of-probation review
Measured savings and benefits
Saves 3 to 8 hours of coordination per hire between HR, IT and the manager. For a small business hiring 1 to 4 people a month, that is 5 to 30 hours saved per month in total. Side benefits: a better first-day experience (onboarding satisfaction up 20 to 35 points), lower turnover in the first 3 months, and consistent onboarding (no more new hires missing key access).
Implementation tip
Build a “role x tools” matrix in a Notion or Airtable table: each role (sales, support, finance, etc.) triggers a sub-workflow that adds the specific access (CRM, business apps, shared folders). This lets you add new roles without touching the main n8n workflow.
Sync inventory between e-commerce and ERP in real time
Department: Operations / E-commerce. Savings: 15 to 40 hours per month. Complexity: Advanced. Tools: Shopify / WooCommerce / PrestaShop + ERP (Sage, Odoo, NetSuite) + email.
Trigger
Triple trigger: order placed on the store (stock decrement), supplier delivery received in the ERP (stock increment), approved customer return (conditional stock increment).
n8n workflow steps
- E-commerce order webhook with the list of SKUs sold
- Immediate stock update in the ERP via API call
- Hourly cron job checking the gap between ERP stock and stock shown on the store
- If the gap exceeds a threshold: automatic reconciliation with an incident log
- If stock falls below the minimum: email alert to the buyer to reorder
- If completely out of stock: automatically hide the product on the store
- Reverse workflow on supplier delivery: update the store from the ERP
- Daily email report of sync incidents to the operations manager
Measured savings and benefits
For an online store handling 200 to 1,000 orders a month, this saves 15 to 40 hours a month on manual stock management and corrections. Major side benefits: 90 to 100 percent of overselling eliminated (orders accepted for products actually out of stock), fewer returns due to unavailability, and a better customer experience (NPS up 5 to 12 points).
Implementation tip
Define a clear “source of truth” for inventory: by default the ERP is authoritative for the business and the store mirrors it. Document every SKU to exclude from sync (made-to-order products, dropshipping, multi-SKU bundles). Plan a manual fallback mode if either platform is down (Redis queue).
Generate a quote automatically from a form
Department: Sales. Savings: 8 to 20 hours per month. Complexity: Intermediate. Tools: Form (Typeform, Tally) + Google Docs / DocuSign + CRM + email.
Trigger
The prospect fills in a quote configurator on the website or a structured sales form.
n8n workflow steps
- Inbound form webhook with the stated needs (products, quantities, options, urgency)
- Look up the price list in a Google Sheets or Airtable sheet
- Automatically calculate the total price with discounts based on volume and customer profile
- Generate the PDF quote from a Google Doc template with the data injected
- Create the prospect / opportunity record in the CRM with the quote attached
- Email the quote to the prospect with an online acceptance link
- Slack notification to the responsible sales rep with context and a CRM link
- If accepted online within 7 days: trigger the invoicing workflow (use case 01)
Measured savings and benefits
Saves the sales rep 20 to 45 minutes per quote. For a small business producing 30 to 80 quotes a month, that is 8 to 20 hours saved per month. Side benefits: response time cut by a factor of 10 (from 24-48 hours to 5-10 minutes), quote-to-order conversion up 15 to 30 percent, and sales reps freed up for high-value negotiations.
Implementation tip
Limit the workflow to “simple” quotes (standard catalog, predefined options). Above a complexity or amount threshold (typically €25k), route to the sales rep for manual handling to keep a human touch on big deals. Always keep a human in the loop by default on new markets or segments that are not yet well defined.
Monitor competitors and their prices automatically
Department: Marketing / Leadership. Savings: 5 to 10 hours per month. Complexity: Intermediate. Tools: Scraping (ScrapingBee, Apify) + AI (summaries) + Notion / Slack.
Trigger
Daily or weekly cron job depending on how critical the monitoring is (prices: daily, communications: weekly).
n8n workflow steps
- Scraping cron job on a list of 5 to 15 competitor URLs (product pages, prices, blog, press releases)
- Structured extraction of the relevant data (prices, product range, new releases, blog headlines)
- Automatic comparison with the previous version stored in the database
- Detect significant changes (price change above 5 percent, new product, blog post)
- If a change is detected: AI call to summarize the nature of the change and estimate its impact
- Slack alert with a summary and a link to the changed page
- Weekly archiving in a structured Notion or Airtable database for trend analysis
- Automated monthly report emailed to leadership with a summary of changes
Measured savings and benefits
Saves 5 to 10 hours a month on manual monitoring (which was often partial and irregular). Side benefits: faster reaction to market moves (alerts within hours vs detection after 2 to 4 weeks), a structured, usable history, and marketing time freed up for higher-value work.
Implementation tip
Check the terms of use of the scraped sites and respect robots.txt. Use a scraping service that handles IP rotation and anti-bot protection (ScrapingBee, Apify) rather than coding the scraping yourself. Calibrate the change thresholds to avoid noise (too many alerts kill attention).
Build a multi-source weekly executive report
Department: Leadership. Savings: 4 to 10 hours per month. Complexity: Intermediate. Tools: CRM + accounting tool + Google Analytics + Stripe / banking + AI + email.
Trigger
Weekly cron job on Monday at 7:00 a.m. to summarize the previous week.
n8n workflow steps
- Monday 7:00 a.m. cron job triggering aggregation of last week’s data
- Pull from the CRM: new deals created, deals won, total pipeline, forecasts
- Pull from accounting: revenue collected, invoices issued, unpaid invoices
- Pull from Google Analytics: traffic, conversions, top sources
- Pull from Stripe / banking: available cash, weekly burn rate
- Comparison with the week before and the previous month (deltas calculated automatically)
- AI call to generate a short commentary on the KPIs (highlights, alerts)
- Generate a formatted HTML email with charts and key KPIs
- Send the report at 8:00 a.m. with the CFO and CIO in copy for any challenge
Measured savings and benefits
Saves 60 to 120 minutes a week for the executive assistant or CFO who used to consolidate KPIs by hand. Over the year, 50 to 100 hours saved. Side benefits: regular reporting (from a random rhythm to a reliable weekly one), consistent metrics (no more conflicting calculations between departments), and faster leadership reaction to business alerts.
Implementation tip
First define the 8 to 12 KPIs that are truly useful to leadership before building the workflow: a rich but unreadable report will not be read. Build the HTML template mobile-first (the CEO reads the report on a phone over Monday morning coffee). Set automatic alert thresholds on critical metrics.
Route and track support tickets with SLAs
Department: Support / IT. Savings: 12 to 30 hours per month. Complexity: Intermediate. Tools: Support email + AI (classification) + Notion / Zendesk / Freshdesk + Slack.
Trigger
Incoming email to support@yourcompany.com or a ticket created in the help desk.
n8n workflow steps
- IMAP trigger on the support mailbox or help desk webhook
- AI call to classify the ticket (category, urgency, customer sentiment, language)
- Look up the customer in the CRM to retrieve context (segment, contract, history)
- Automatic routing to the right agent by category and current workload (weighted round-robin)
- Apply the SLA by customer segment (Premium: 2h, Standard: 8h, Basic: 24h)
- Slack notification in the team channel with enriched context and a direct link to the ticket
- Automatic response-time tracking and an alert when the SLA is at risk (at 80 percent of the deadline)
- If the SLA is breached: automatic escalation to the support manager with a notification
- Weekly report of SLAs met by category and agent
Measured savings and benefits
For a small business receiving 200 to 600 tickets a month, this saves 12 to 30 hours a month (no more manual triage, misrouting, or SLA tracking in Excel). Major side benefits: SLA compliance rising from 65-75 to 92-98 percent, customer satisfaction (CSAT) up 15 to 25 points, and structured data to manage support (volumes by category, productivity by agent).
Implementation tip
Document the categories and their criteria precisely before launching AI classification: 8 to 15 categories at most are manageable (beyond that, classification degrades). Keep a human in the loop for the first 4 weeks to validate and correct the AI classifications while you refine the prompt.
Publish tailored content on every social network
Department: Marketing. Savings: 3 to 8 hours per month. Complexity: Simple. Tools: CMS (WordPress) + AI (adaptation) + LinkedIn, Twitter, Facebook, Instagram APIs.
Trigger
A new blog post is published on the site (CMS webhook) or added manually to a Google Sheet scheduling list.
n8n workflow steps
- CMS webhook when a new post is published
- Retrieve the title, summary and main image
- AI call to generate a tailored LinkedIn post (1,200-1,500 characters, expert tone)
- AI call to generate a tailored Twitter thread (4-7 tweets, strong hook)
- AI call to generate a tailored Facebook post (350-500 characters, more emotional)
- Human approval pending in a Slack channel (1 click to approve each variant)
- Scheduled publishing at the best times per network (LinkedIn 8-10 a.m., Twitter 12-2 p.m., Facebook 6-8 p.m.)
- Automatic engagement tracking (likes, shares, comments) over 7 days
Measured savings and benefits
For a small business publishing 2 to 6 posts a month, this saves 3 to 8 hours of community management. Side benefits: consistent publishing (from a random rhythm to a systematic one), a consistent editorial line, and an engagement dataset to optimize future content.
Implementation tip
Always keep human approval in the loop before publishing, especially on LinkedIn where the corporate tone must be controlled. Build network-specific prompts (LinkedIn ≠ Twitter ≠ Facebook) rather than one generic prompt. Include 3 to 5 examples of past high-performing posts in the prompt to calibrate the style.
Automatically file and sort incoming attachments
Department: Sales admin / Finance / Leadership. Savings: 5 to 12 hours per month. Complexity: Simple. Tools: Email + AI (categorization) + Google Drive / SharePoint / Dropbox.
Trigger
An email with an attachment arrives at a dedicated address (invoices@, contracts@, quotes@) or is detected automatically in a shared inbox.
n8n workflow steps
- IMAP trigger filtered on emails with PDF attachments
- Extract the attachment’s text via OCR if needed (scanned PDFs)
- AI call to classify the document (supplier invoice, contract, customer quote, delivery note, letter)
- Structured extraction of metadata (issuer, date, amount, document number)
- Standardized file renaming (e.g. 2026-05-20_invoice_OVH_4567.pdf)
- Automatic filing in the right Drive / SharePoint folder by category and year
- Add a row to a tracking sheet (Google Sheets or Notion) with a link and metadata
- If it is a supplier invoice: send it to the relevant manager for payment approval
Measured savings and benefits
For a small business receiving 100 to 400 documents a month, this saves 5 to 12 hours a month on manual sorting and filing. Side benefits: zero lost documents (vs 5 to 15 percent typically with manual filing), keyword search across all archives, and better document compliance for accounting or GDPR audits.
Implementation tip
Define the target folder structure before launching the workflow: changing the tree afterwards is costly. Validate OCR quality on a sample of 50 representative documents before scaling up (native PDFs vs scans vs photos). Keep a “To file manually” folder for documents the AI does not recognize.
Send a post-delivery NPS survey and act on the answers
Department: Marketing / Customer Success. Savings: 2 to 6 hours per month. Complexity: Simple. Tools: ERP / CRM + Typeform / internal form + AI (verbatim analysis) + Slack / Notion.
Trigger
A delivery or service is marked as completed in the ERP or CRM. The workflow waits 7 days to give the customer time to try the product or service.
n8n workflow steps
- ERP webhook when the delivery or service is closed
- 7-day delay via a Wait node
- Send an email with a link to a short NPS Typeform (1 score + 1 comment)
- If no answer by D+10: a single reminder by text or email
- When the answer comes in: record the score and comment in the customer’s CRM record
- If Promoter (9-10): trigger a workflow asking for a Google review or testimonial
- If Detractor (0-6): immediate Slack alert to the CS manager for a callback within 24h
- Monthly AI call to analyze the comments (recurring themes, overall sentiment)
- Automated monthly report to the leadership team with NPS and top themes
Measured savings and benefits
For a small business with 50 to 300 deliveries a month, this saves 2 to 6 hours a month on manual sending and processing. Major side benefits: unhappy customers detected in under 48 hours (vs 2 to 6 weeks with a quarterly survey), response rates typically rising from 12-18 to 30-45 percent thanks to optimal timing, and a reliable, continuous NPS barometer for decision-making.
Implementation tip
Keep the survey ultra-short (1 score + 1 comment): any survey with more than 3 questions cuts the response rate by 2 or 3. The callback to a Detractor must always be made by a person within 24h (never an auto-reply): that is what turns a churn risk into a loyalty opportunity. Never send NPS surveys to customers in an active dispute.
Recommended quick wins by type of small business
Not all workflows are equal for every company profile. Here are the top 3 recommended per business type to start a program with quickly demonstrable ROI.
| Business profile | Workflow #1 | Workflow #2 | Workflow #3 |
|---|---|---|---|
| B2B services company | 01 - CRM-accounting sync | 02 - AI lead qualification | 03 - Invoice reminders |
| E-commerce / D2C | 05 - ERP inventory sync | 12 - Post-delivery NPS | 10 - Multi-network publishing |
| Manufacturing SMB | 03 - Invoice reminders | 05 - ERP inventory sync | 08 - Executive report |
| SaaS / Tech | 09 - Support ticket SLAs | 02 - AI lead qualification | 12 - Post-delivery NPS |
| Fast-growing SMB | 04 - Employee onboarding | 01 - CRM-accounting sync | 08 - Executive report |
| Multichannel SMB | 11 - Document filing | 10 - Multi-network publishing | 07 - Competitive monitoring |
For a complete scoring grid tailored to your context, run the phase 1 mapping described in our 6-phase methodology. For broader programs involving generative AI and autonomous agents, see our guide to AI agents for business.
Frequently asked questions about n8n use cases for small businesses
Can we roll out all 12 workflows in the first year?
It is technically possible but rarely advisable. A small business structures its program better by aiming for 12 to 25 active workflows at 12 months, rolled out in waves of 3 to 6 every 6 to 8 weeks. Start with 3 to 5 quick-win workflows from the top of the table above, measure the real ROI over 3 months, then pick up the pace. Trying to stack all 12 from the start overloads your resources and raises the overall risk of failure.
Do these workflows also work on Make or Zapier?
Yes, the 12 use cases presented are conceptually portable to Make or Zapier. The differences are mostly in implementation: Zapier is faster to set up for simple workflows (use cases 03, 10, 11, 12) but gets expensive beyond 2-5k tasks a month. Make excels at visual workflows with complex branching (use cases 04, 09). n8n wins for high-volume workflows, GDPR-driven self-hosting needs, or workflows that rely heavily on Code nodes (use cases 02, 05, 07). See our full n8n vs Make vs Zapier comparison.
How much does a full rollout of the 12 workflows cost?
For a small business with 30 to 80 employees, the full budget to set up the 12 workflows ranges from €25k to €60k over 9-12 months: €15k to €35k of outside services (design, configuration, training), €4k to €12k of annual platform licensing, and €6k to €13k of internal time from the no-code lead. Typical payback comes between months 7 and 12, for a net return on investment over 18-24 months. See our detailed cost and ROI analysis.
How do you handle outages or errors on these critical workflows?
Five reliability practices. First, set up an Error Trigger node on every workflow that automatically notifies the lead when an execution fails. Second, add automatic retries with exponential back-off on nodes prone to transient errors (API calls). Third, keep an isolated test environment to validate any change before production. Fourth, monitor critical workflows from a central dashboard (n8n Executions, Datadog, Grafana). Fifth, document a runbook per workflow (what to do on error, who to contact, how to replay executions).
Are these use cases GDPR-compliant for a small business in France?
Yes, with three precautions. First, self-host n8n on a VPS located in France or the EU (OVH, Scaleway, Hetzner) for workflows that handle sensitive personal data. Second, for workflows that use AI (use cases 02, 07, 09, 11, 12), use GDPR-compatible services: Mistral AI (France), Azure OpenAI with EU data residency, or Anthropic via AWS Bedrock in an EU region. Third, record the automated processing in the DPO’s GDPR register of processing activities, especially scoring workflows (use case 02), which may fall under GDPR Article 22 on automated decision-making. See also our GDPR guide for small businesses (2026).