Business process automation with n8n: the first 6 automations and how to set them up
Every business has dozens of small tasks that repeat daily: copying a web form enquiry into the CRM, telling accounts when a quote is approved, emailing a supplier when stock runs low, preparing the sales report every Monday. Each takes a few minutes, but together they add up to hours per week, and because they are done by hand, they carry a risk of error. n8n is a workflow automation tool for automating this kind of work with little or no code.
What is n8n?
n8n is an automation platform that connects applications and systems in a visual workflow editor. Each workflow starts with a trigger (a new form submission, an incoming email, a schedule, a webhook call) followed by steps (transform data, send it to an API, branch on a condition, send a message).
It offers hundreds of ready-made integrations, including Google Workspace, Microsoft 365, Slack, HubSpot, Shopify, WooCommerce and databases. Systems without a ready-made integration can be connected via their APIs using HTTP requests. JavaScript or Python code can be added inside workflows, and AI models can be used as steps.
How does it compare with Zapier and Make?
- Hosting: n8n can run on your own server (self-hosted), which matters for organisations that want data to stay on their own infrastructure. Zapier and Make are cloud-only services.
- Pricing model: Cloud tools usually charge per task or operation, so costs can grow quickly for high-volume workflows. With self-hosted n8n, cost is mainly the server.
- Flexibility: Code steps, complex branching and error handling are more flexible in n8n. Tools like Zapier, on the other hand, are easier for non-technical users to start with.
- Licence: n8n is distributed under a "fair-code" model. The self-hosted Community edition can be used free of charge for a company's own internal processes; uses such as reselling n8n as a product are restricted by the licence. Check the current licence terms before starting a project.
The first 6 automations most businesses build
1. Lead management
Every enquiry from the website form, email or WhatsApp is recorded in the CRM, assigned to the right sales rep and acknowledged with a "we've received your request" message. A reminder goes to a manager if there is no reply within 24 hours.
2. Quote and approval flow
Quotes above a certain value are routed to a manager for approval. Once approved, the quote PDF is generated, sent to the customer and the CRM status is updated.
3. Order and stock notifications
Orders from the online shop are passed to the warehouse team, and when stock drops below a threshold, purchasing and the supplier are notified.
4. Invoice and payment follow-up
Invoices that are due or overdue are read from the accounting system, a polite reminder is sent to the customer and a daily list is prepared for the collections team.
5. Recurring reports
Every Monday morning, sales, website traffic and ad spend are collected from different sources and sent to management as a single summary by email or Slack/Teams.
6. AI-assisted classification
Incoming emails or support requests are read by an AI step that identifies the topic (complaint, quote request, technical support), urgency and language, routes the request to the right person and drafts a reply where appropriate. A person still makes the decision, but triage time drops dramatically.
Hosting options
- n8n Cloud: No server management and a quick start. It is a monthly subscription and data is processed on n8n's cloud infrastructure.
- Self-hosted: Installed on a cloud server with Docker. You keep control of the data; backups, updates and security become your responsibility or that of your service provider.
Which is right depends on the sensitivity of the data, workflow volume and in-house technical capacity.
What to watch out for
- Error handling: What happens when an API is temporarily unavailable? Retries, error notifications and a list of failed records should be designed from the start.
- Credentials: API keys should never be written into workflows as plain text; use n8n's credential manager.
- Logging and traceability: It should be clear which record passed through which workflow, when and with what result.
- Ownership: Every workflow needs an owner. If nobody knows what a workflow does once its author leaves, the automation becomes a risk.
- Personal data: Workflows that process customer data must comply with GDPR or UK GDPR, especially when data is transferred to third-party services.
Where to start
The best starting point is the task that repeats most often each week and has the clearest rules. Measure how long it takes today, automate it and measure again a month later. To decide which tasks are worth automating, use the method in which processes to automate and how to calculate ROI.
uurstudios reviews your workflows, identifies the steps best suited to automation and handles setup, testing and maintenance with n8n, Make or custom software. See the services overview for details.