Workflow automation means a task that runs through several of your tools, step by step, without someone copying details from one screen to the next. A form is submitted, a deal is marked as won, an order arrives: the automation picks up that event and carries out the steps a person would have done by hand. This page is for UK small and medium-sized businesses where staff re-type the same information into a CRM, a spreadsheet, an accounting package and an email. I map the process with you, build the workflow in your own accounts and hand it over documented, so it keeps running after I step away.
What workflow automation fixes
Manual hand-offs fail quietly. An enquiry sits in a shared inbox over a bank holiday weekend. A new client is added to the CRM but nobody creates the folder or sends the welcome pack. The invoice goes out with last month’s address because the update only reached one system. Each slip is small, but they repeat, and the customer is usually the one who notices first.
A well-built workflow does the same steps, in the same order, every time. Each record carries its source and a time stamp, and the people who need to act are told straight away. Your team stops being the glue between systems and spends that time on the parts of the job that need judgement.
Who it suits, and who it does not
It suits a business that can describe a task as a sequence: when this happens, do that, then that. The task should happen often enough to matter, say several times a week, and follow the same rules most of the time.
It does not suit a process that changes every month, one nobody can yet describe, or one that runs twice a year. If the steps themselves are muddled, automating them only makes the muddle run faster. In that case I would sort the process on paper first, and sometimes that alone solves the problem.
What the work covers
Mapping the process before building anything
I start by writing down how the task runs today: who does what, in which tool, with which information, and what happens when something is missing. That map usually exposes steps nobody needs and decisions nobody owns. It also becomes the specification for the build, so you can check it before a single step is configured.
Triggers, steps and branches
Every workflow starts with a trigger. The fastest kind is a webhook, where one system notifies the next the instant something happens rather than being checked on a timer. From there the workflow filters, branches and acts: a large order goes to one person, a small one to another; a returning customer is updated rather than created twice.
Moving data cleanly between tools
Most of the effort sits in the joins. Field mapping decides which value in one tool lands in which field of the next, and how dates, phone numbers and postcodes are formatted on the way. Where two systems both edit the same record, I decide with you whether a two-way sync is really needed, because it is the setup most likely to overwrite good data with stale data.
Error handling and alerts
Every connection fails at some point: a password changes, a supplier’s API is down for an hour, a required field arrives empty. I build in retries, a named person who is alerted when a run fails, and a log of what went through, so a failure is noticed the same day rather than at month end.
Documentation and handover
You receive a plain-English runbook for each workflow: what starts it, what it does, which accounts it depends on and what to do when it stops.
Workflows that usually repay the effort
- New enquiry handling. A website form or Facebook lead ad enquiry lands in your CRM, the enquirer gets an acknowledgement and the right person is told in Microsoft Teams, Slack or email.
- Won deal to delivery. When a deal is marked as won, the workflow creates the client in Xero or QuickBooks, sets up a project in your task tool, creates a shared folder and sends the onboarding email.
- Bookings and follow-ups. A booked call updates the CRM record, and a missed one triggers a polite rebooking message.
- Internal approvals. A request for a discount, a refund or a purchase is routed to the person who signs it off, with the answer recorded against the original record.
- Weekly housekeeping. Duplicate contacts are flagged, overdue tasks are listed and the summary arrives in one message on Monday morning.
Choosing the platform
The platform follows the workflow, not the other way round. Zapier is quick to set up and easy for a non-technical team to maintain; Make handles branching and lists of records well; n8n can be self-hosted, which matters when data must stay on servers you control. The glossary entry on Zapier and Make explains how the two differ. Sometimes the right answer is the automation already built into your CRM or accounting software, at no extra subscription cost.
Before recommending one I weigh how many runs a month you expect, how complicated the logic is, who will maintain it after handover and where the data is processed, because platform pricing and data location vary more than the feature lists suggest. You can see the software I work with on my tools I use page.
How I run a build
- Scoping call. We pick one task, agree what a finished workflow does and what it does not do, and list the accounts I will need access to.
- Process map. I send the written map for you to correct. Nothing is built until you agree it.
- Build in your accounts. The workflow is created under your organisation’s login, not mine, so you own it from day one.
- Test with real cases. I run it against real examples, including the awkward ones: a missing email address, a duplicate customer, a cancelled order.
- Supervised launch. It runs live while we check the results for a short agreed period before it is left alone.
- Handover. You receive the runbook, the alert settings and a short walkthrough for whoever will look after it.
Problems I see most often
- Built under one person’s login. When that freelancer or employee leaves, their connections expire and the workflow stops without warning.
- No failure alerts. The automation has been silently failing for weeks and nobody knew until a customer chased.
- Duplicates everywhere. Each run creates a new contact instead of finding the existing one, so the CRM fills with copies of the same person.
- Undocumented chains. One workflow triggers another, which triggers a third, and no one can say which step does what.
- Tracking left behind. Enquiries move automatically, but the source of the lead is lost on the way, so you cannot tell which channel produced the work. My guide on checking your conversion tracking works covers the measurement side.
UK GDPR in automated workflows
Every tool that a workflow passes personal data through is a processor acting for your business. Before building, I list each one, check where it processes data and whether you have a data processing agreement in place with it. I also apply data minimisation: the workflow carries only the fields the next step needs, not the whole record. Where a workflow sends marketing email or texts, PECR consent rules apply as well, and the workflow should record the consent it relies on. This is practical housekeeping rather than legal advice; for anything unusual, speak to a data protection adviser.
What you receive
- A written process map, agreed before the build.
- The working workflow, in accounts your business owns.
- Failure alerts sent to a named person, and a run log.
- A plain-English runbook and a list of every connected account.
- A short walkthrough for the person who will maintain it.
Pricing
Cost depends on the number of tools involved, how many branches the logic needs and how much testing the edge cases demand. A single workflow joining two tools is a small job; a chain across a CRM, accounting software and a booking system is a larger one. Platform subscriptions are paid by you, directly to the provider. Each quote is written in GBP after a free first call, once the scope is clear, and agreed in writing before any work starts.
Next step
Pick the one task your team complains about most and describe it in a few lines: what starts it, which tools it touches and who does it now. Then book a free 30-minute call and I will tell you whether it is worth automating, which platform I would use and what the first version would do.