Workflow automation
n8n Workflow Automation
n8n connects the tools a business already uses, so data moves between them without anyone copying it by hand. We set it up on a server you own, build the workflows, and keep them running after launch.
What n8n automation is for
Most offices have a job like this. An enquiry arrives through the website form. Someone copies it into a spreadsheet, then into the CRM, then sends a WhatsApp message to whoever handles that area. It takes a few minutes, happens many times a day, and gets skipped on a busy afternoon.
n8n is an open-source tool for automating that kind of work. A workflow is a chain of steps: when this happens, fetch that, change it, and send it there. It has ready-made connectors for hundreds of apps, and where there is none it can call any API directly. A step can also be handed to an AI model, for example to sort incoming email or pull the fields out of an invoice.
For most of the businesses we talk to, we would pick it over Zapier or Make. It runs on your own server, so customer data does not pass through another company’s cloud, and the cost stays flat as the number of runs goes up.
Most of the work in a project like this is about the process. A workflow copies whatever the business does, mistakes included, so every project starts by writing down what actually happens today.
Is this the right fit?
Worth automating when
- Staff copy the same data between two or more tools every day
- Leads, orders or bookings arrive in one place and are needed in another
- Your Zapier or Make bill goes up every month
- You want customer data to stay on a server you control
Leave it manual when
- The task comes up a few times a month, where doing it by hand costs less
- The tools involved have no API and no export, so there is nothing to connect
- The process itself is unclear or changes every week. That needs settling first
- You need a full custom application, which is a separate project
What you get
A self-hosted setup
n8n installed on your server or cloud account, with HTTPS, backups and updates, so the workflows and the data belong to you.
Workflows written down
Every workflow is named, commented and described in plain language, so someone new can see what it does without opening each step.
Failures that get noticed
When a step fails, the run is retried or a person is told. A workflow that fails silently is worse than having none.
AI steps where they help
Sorting incoming email, reading an invoice or drafting a reply, with a person approving anything that goes out to a customer.
Care after launch
APIs change and login tokens expire. A small monthly allowance covers the fixes, so nothing stops quietly in month three.
How a project runs
-
Map the work
We sit with the person who does the task today and write down every step, including the ones they do without thinking.
-
Choose what to automate
Some steps should stay with a person. We agree on the repetitive, rule-based ones and leave the judgement calls alone.
-
Run it side by side
For a week or two the workflow runs next to the manual process, so the results can be compared before anyone stops checking.
-
Hand over
Logins, documentation and a short walkthrough for your team, plus monthly care if you want it.
Built with
The platform and the tools around it. Nothing here is chosen because it is new.
- n8n
- Docker
- PostgreSQL
- Node.js
- Webhooks
- REST APIs
- Google Workspace
- WhatsApp Business API
Questions we get asked
Why n8n and not Zapier?
Zapier is quicker to start and fine for a few simple workflows. n8n suits a business that runs many of them, handles customer data or needs custom steps, because it runs on your own server and its cost does not grow with every task.
Do we need our own server?
A small cloud server is enough for most businesses, and we can set it up in your account so you own it. If you would rather not run a server at all, n8n also sells a hosted version.
What happens when one of our tools changes?
Sometimes a workflow breaks. The error alerts tell us first, and the monthly care covers the fix.
Will it work with the software we already use?
If the software has an API, or can export and import files on a schedule, n8n can usually work with it. We check each tool before we quote.
Have you built this for clients before?
Not yet as a named client project, and we would rather say so up front. The pieces it is made of, APIs, webhooks, databases and servers, are what our team works with every day.
What does it cost?
It depends on how many workflows you need and how complex they are. After we map the work you get a fixed quote for the build. The server itself usually costs little.
Tell us the task your team repeats most.
Describe it step by step in a few lines. We will tell you whether it is worth automating and roughly how we would do it.