Every business has tasks that happen over and over in the same way. An order comes in, someone copies the details into a spreadsheet, sends a confirmation email, updates the stock count, and notifies the warehouse. That sequence of actions — triggered by one event, following the same steps every time — is a workflow. And if it's happening manually, it can almost certainly be automated.
Workflow automation is the process of using software to run these sequences automatically, without a human doing each step. This article explains what it is, what it can and can't do, and how to work out whether it's worth doing for your business.
If someone on your team spends more than two hours a week doing the same repeatable task that follows predictable steps, it can almost certainly be automated. That's the threshold we use when auditing a business's operations.
What workflow automation actually does
Automation tools like Make (formerly Integromat), Zapier, and n8n work by connecting the software you already use and triggering actions automatically when something happens. A trigger is an event — a new form submission, a new order, a new row in a spreadsheet. An action is what happens next — send an email, create a task, update a record, send a WhatsApp message.
The power comes from chaining these together into multi-step workflows that run without any human involvement.
Real examples of automated workflows
What automation can't do
Automation is not the same as artificial intelligence, and it's important to understand the difference. Automation follows rules — if this happens, do that. It doesn't think, adapt, or make judgement calls. It handles the predictable and repeatable, not the complex and variable.
A good automation handles 80% of a process automatically and passes the remaining 20% — the edge cases, the unusual situations — to a human. Trying to automate the unpredictable parts usually creates more problems than it solves.
- Automation is good for: repetitive, rule-based tasks with predictable inputs and outputs
- Automation is not good for: complex decisions, nuanced customer conversations, anything that requires judgment
How to tell if a process is worth automating
Not every process should be automated. Some tasks are too variable, too low-frequency, or too important to trust to a system without careful setup. Here's how to evaluate whether something is a good candidate.
Questions to ask about any process
- Does this happen the same way every time, or does it vary significantly?
- How many times per week or month does this happen?
- How long does it take a human to do it each time?
- What happens if it's done incorrectly or late?
- Does it require judgment, or is it purely mechanical?
If the answer is: it's consistent, it happens frequently, it takes meaningful time, mistakes have consequences, and it's mechanical — then it's a strong automation candidate.
What does automation actually cost?
The most common tools — Make, Zapier, n8n — have free tiers for simple workflows and paid plans starting from around £10–50/month depending on volume. The real cost is the setup time and maintenance, which is where working with a partner makes sense for complex multi-step workflows.
For most small businesses, the economics are straightforward: if an automation saves two hours per week and a team member's time costs £15/hour, that's £120/month saved. A £30/month tool subscription pays for itself in less than a week.
Where to start
Start with the process that causes the most friction in your business right now. Not the most technically interesting one. The one your team complains about most, the one that causes the most errors, or the one that happens most often.
- Write down the steps from trigger to completion
- Identify every tool involved in the process
- Check whether those tools have integrations with Make or Zapier (most do)
- Build the simplest version of the automation first
- Test it with real data before going live
- Monitor it for the first two weeks and fix edge cases as they appear
Workflow automation isn't about replacing your team. It's about removing the parts of their work that a computer should be doing — so they can focus on the parts that actually require a human. That's the only goal worth optimising for.