10 n8n automations worth implementing in a small business

Most small businesses don't need a programmer to get back several hours every week. All you need to do is stop manually copying data from one window to another. In this guide, we've gathered 10 n8n automations that work well for companies with between one and a dozen employees. For each one, we explain what triggers it, what nodes it consists of, and how much time it realistically saves. If you're just starting and don't know what n8n is, read our guide What is n8n and how to automate a business without a programmer first.

Table of contents

• Where to start automating in a small business?
• 1. How to automatically save contact form submissions?
• 2. How to send reminders about unpaid invoices?
• 3. How to transfer orders from a store to a spreadsheet or accounting system?
• 4. How to automatically confirm meetings and send reminders?
• 5. How to organize company email and answer common questions?
• 6. How to get notified when a website goes down?
• 7. How to collect customer feedback after a purchase?
• 8. How to add new customers to a newsletter and CRM?
• 9. How to publish content across multiple channels at once?
• 10. How to build a simple AI assistant for your team?
• How much time and money does this save?
• Where to run n8n so automations work around the clock?
• Which mistakes to avoid when automating?
• Summary
• FAQ: automations in n8n

Where should you start with automation in a small business?

Before you open the n8n editor, make a simple list. For a week, write down every task you perform more than three times and that involves moving information from one place to another. Typical examples include copying an order into a spreadsheet, answering the same customer question, sending a payment reminder, or checking whether a website is working.

A task is suitable for automation if it meets three conditions:

• repeats at least a few times a week,
• has clear rules, meaning you can describe it with the sentence "when X, do Y",
• does not require human judgment, or a person only approves the result.

Start with the one automation that takes up the most of your time, not with ten at once. Every workflow in n8n consists of a trigger (what starts it) and subsequent nodes (what should happen). The examples below are arranged from the simplest to the more advanced.

1. How to automatically save contact form submissions?

Problem: inquiries from the form on the landing page end up in the inbox, get lost among newsletters, and no one knows whether a reply has already been sent.

Workflow: the Webhook node receives data from the form, the Google Sheets node (or a database in Baserow) adds a row with the name, email, and message, and the Send Email node automatically sends the customer a confirmation: “We received your inquiry, we will reply by tomorrow”. Finally, the team receives a notification in the messenger.

Benefit: every inquiry has its own row and status, and the customer gets a reply right away. WordPress forms (Contact Form 7, WPForms, Gravity Forms) can send data to a webhook URL via a plugin or a simple code snippet.

2. How to send reminders about unpaid invoices?

Problem: checking who has not paid and writing polite reminders is work nobody enjoys and that is easy to put off.

Workflow: the Schedule Trigger node runs the workflow every day at 9:00. The HTTP Request node or a ready-made integration retrieves a list of overdue documents from your invoicing software. The IF node splits them into groups: 3 days overdue and 14 days overdue. Each group receives different email content via Send Email.

Benefit: reminders always go out, rather than when someone remembers. If you do not yet have invoicing software with an API, you can set up an open-source Invoice Ninja instance alongside n8n, which n8n supports with a ready-made node.

3. How to transfer orders from your store to a spreadsheet or accounting software?

Problem: A WooCommerce store owner exports orders to CSV every week and pastes them into a spreadsheet for their accountant.

Workflow: The WooCommerce Trigger node responds to new orders. The Set node selects only the required fields, including order number, date, amount, country, and payment method. The Google Sheets node adds a row to a spreadsheet shared with the accounting office.

Benefit: The report is always up to date, and the end-of-month export is no longer needed. The same workflow works for PrestaShop and other stores with an API.

4. How to automatically confirm appointments and send reminders?

Problem: clients forget about scheduled appointments, and each “is it still on tomorrow?” call takes several minutes.

Workflow: the booking system (for example Cal.com or Kalendarz Google) starts the workflow when a new booking comes in. n8n sends a confirmation immediately, while the Wait node waits until the day before the appointment and sends a reminder by email or SMS through an API gateway.

Benefit: fewer no-shows and no manual calls. In clinics, salons, and advisory firms, this is usually the automation on the list that makes the quickest impact.

5. How to organize company email and answer common questions?

Problem: the info@ mailbox receives a mix of quote requests, complaints, invoices, and spam, and someone has to sort it every day.

Workflow: the Email Trigger (IMAP) node reads new messages from the mailbox. The IF or Switch node checks the subject and sender: invoices go to the accounting folder, complaints to customer support, and quote requests to the lead spreadsheet. A more advanced version passes the content through an AI node, which classifies the message and suggests a draft response for approval.

Benefit: nothing gets lost in the inbox, and the initial sorting happens automatically. If you have company email on Saplo, n8n connects to it using standard IMAP and SMTP, with no additional services.

6. How do you get notified when the website goes down?

Problem: the company finds out about the website outage from a customer, sometimes only after several hours.

Flow: Schedule Trigger every 5 minutes, HTTP Request to the homepage and store, IF checks the response code and load time. If something is wrong, a notification goes to your phone, for example via ntfy, which sends a push notification with a single HTTP request.

Benefit: you respond within minutes, not hours. If you want full monitoring with charts and a status page, a separate tool such as Uptime Kuma will work better. Leave n8n for responses, such as creating tasks in a task management system.

7. How to collect customer reviews after a purchase?

Problem: satisfied customers rarely write a review on their own, and a manually sent request usually gets lost among everyday responsibilities.

Flow: the trigger is a fulfilled order or a closed work order. The Wait node waits, for example, 7 days, then Send Email sends a brief request with a link to a Google Business Profile or a survey. Survey responses, such as those from Formbricks, return to n8n, and low ratings go straight to the owner before the customer mentions the issue publicly.

Benefit: a steady stream of reviews without having to remember to ask for them, and a quick response to dissatisfied customers.

8. How to add new customers to your newsletter and CRM?

Problem: the same customer data has to be entered into the CRM, mailing list, and spreadsheet.

Flow: a single source (an order, form, or signed contract) triggers a workflow that creates a contact in the CRM (for example, Twenty) and adds them to the list in Listmonk, provided the customer has given marketing consent. The IF node ensures that a contact is not added to the newsletter without consent.

Benefit: all data in one place and GDPR compliance, because the consent rule is saved in the workflow rather than in someone's memory.

9. How to publish content across multiple channels at once?

Problem: a new blog post has to be manually shared on Facebook, LinkedIn and in the newsletter.

Workflow: the RSS Feed Trigger node detects a new post. The AI node shortens it into a version for social media, while the following nodes publish the post or save a draft for approval. It is safer to start with the draft version because an automated publishing workflow without oversight can push a typo to three places at once.

Benefit: one publication instead of four. This automation works well with point 8.

10. How to Build a Simple AI Assistant for Your Team?

Problem: employees keep asking the same questions: pricing, return procedures, invoice details, the office Wi-Fi password.

Flow: n8n has AI Agent and Chat Trigger nodes that you can use to build a chat assistant that answers questions based on your documents. The language model can come from a paid API (OpenAI, Anthropic) or your own server, and you can use something like Open WebUI to provide the team interface.

Benefit: fewer work interruptions and consistent answers. This is the most advanced item on the list, so do it last, once the simple workflows are already working.

How much time and money does it save?

Let's calculate conservatively. If each of the five implemented automations saves 20 minutes a day, over a month with 21 working days, that's 35 hours. Even at a rate of $10 per hour of work, that's $341 per month that the team can dedicate to client work.

The second part of the equation is the cost of the tool. Zapier's Professional package costs about $19 per month according to our comparison and has a task limit, so the price increases with higher traffic. n8n running on your own server has no execution limit, and you only pay for the server. For a detailed comparison with Zapier and Make, see our n8n guide.

Where should you run n8n so your automations work around the clock?

An automation that only runs when your laptop is on isn't really an automation. n8n needs to run on a server that works non-stop, has a domain with an SSL certificate (otherwise webhooks from forms and stores won't work properly) and keeps a backup of your workflows.

On Saplo, you can install n8n with one click from the App catalog. It runs on the official n8n Docker image in its own container, with a domain and a free SSL certificate. When you first sign in, n8n shows a screen for creating the owner account, so the panel isn't open to everyone.

How to choose a plan:

• Box M ($69 per year, 2 GB RAM) is enough for n8n with several simple workflows. n8n requires a minimum of 1 GB of memory, so you'll have some headroom.
• Box L ($149 per year, 6 GB RAM) makes sense when a website, a store and several other apps from this list run alongside n8n.
• Box XL ($329 per year, 12 GB RAM) is the right choice when n8n processes large amounts of data, handles AI agents or shares a server with resource-heavy apps such as Nextcloud.

You can try every plan for 7 days without providing a card details, and you can upgrade to a higher plan with no downtime. For current prices and specifications, see the Price list.

Which mistakes to avoid when automating?

• No error handling. Set up a workflow in n8n with an Error Trigger node that sends a notification whenever any automation crashes. Otherwise, you'll find out about the problem a week later.
• Passwords entered in nodes. Keep login details in saved credentials (Credentials), not in the content of nodes that someone could export and share.
• A full automation where a draft will do. To start with, save emails to clients and public posts as drafts for approval.
• No testing with real data. Before enabling the workflow, run it manually on a few real examples and check every node.
• Ten automations in one weekend. Roll them out one at a time and give each one a week before adding the next.

Summary

Simple automations deliver the fastest return: a form connected to a spreadsheet, meeting and invoice reminders, and email sorting. An AI agent and publishing across multiple channels are the next step. Start with the one task that annoys you the most, build it in n8n, test it for a week, and only then add more. If you want n8n on a server without configuring Docker or certificates, you can launch it on Saplo in just a few minutes.

FAQ: automations in n8n

Do you need to know how to program for these automations?

No. Every workflow in the list is built from ready-made nodes in the visual editor. Code (the Code node with JavaScript or Python) only becomes useful for unusual data transformations.

How many automations can run in n8n at the same time?

On your own n8n server, there is no limit to the number of workflows or executions. The server's memory and processor are the limiting factors, so as the number of workflows grows, you should consider moving to a plan with more RAM.

Will n8n connect with Polish services that don't have a ready-made node?

Yes, as long as the service has an API. The HTTP Request node can send any request, so you can connect an app to an invoicing system, SMS gateway, or courier system, even when n8n has no dedicated integration for it.

What happens to automations when the server restarts?

Workflows are stored in the n8n database and restart automatically after a reboot. On Saplo, the n8n container starts automatically, and backups are taken daily, including off-site.

Can I move ready-made automations from another n8n server?

Yes. Workflows are exported from n8n as JSON files and imported on the new server. You then need to add the credentials manually because, for security reasons, they are not transferred in a standard export.