Zapier is the automation tool most UK businesses meet first. A Zap watches one app for an event, such as a new form entry, a paid invoice or a booked call, and then carries out actions in other apps without anyone copying data across by hand. This page is for businesses that already run Zaps they no longer trust, and for those deciding whether Zapier is the right platform before they commit. I plan, build and document Zaps inside your own Zapier account, and I will tell you plainly when another tool would serve you better.
What Zapier is good at
Its main strength is reach. Zapier’s app directory is very large, so the CRM, booking system or accounting package you already pay for almost always has a ready-made connection. That keeps builds quick and means fewer custom calls to an API.
The editor is also the easiest of its kind for non-technical staff. Each Zap reads top to bottom as a list of steps, written in ordinary language, so an office manager can open one, see what it does and switch it off if something looks wrong. For a small team without a developer, that matters more than any feature list.
Beyond simple two-step Zaps, the platform covers most everyday needs:
- Paths and filters send records down different branches, or stop them, based on rules you set.
- Formatter steps tidy dates, names, phone numbers and currency before data lands anywhere.
- Webhooks and code steps handle apps without a ready-made connection, as long as they offer a webhook or an API.
- Zap history records every run, so you can see what data arrived and which step failed.
Where Zapier becomes expensive or awkward
Zapier charges by task, and a task is, broadly, each action step that runs successfully; some built-in steps are excluded. A Zap with six ordinary actions uses six tasks every time it fires. That is fine for a few hundred enquiries a month, but a Zap that touches every order line or every row of a spreadsheet can burn through a plan quickly.
Long, branching processes are the other weak point. Once a Zap has several paths, each with its own steps, it becomes hard to follow and harder to change safely. Loops over lists of items are possible but less natural than on Make, and there is no option to run Zapier on your own servers if your data has to stay in-house.
What I build on Zapier
Enquiry capture and follow-up
Website forms, Facebook and Instagram lead ads and booking tools all feed one place: your CRM. Each new contact is checked for duplicates, tagged with where it came from, given an owner and sent a prompt acknowledgement. If the rules for who handles which enquiry are not written down yet, we agree them first, because lead routing that the sales team disagrees with simply gets ignored.
Admin between finance and operations tools
A signed proposal can create a client folder, a project in your task manager and a draft invoice in Xero or QuickBooks. A paid invoice can update the deal stage and notify the account manager. These Zaps rely on careful field mapping so VAT numbers, company names and billing addresses land in the right fields every time.
Notifications people actually read
Instead of everyone watching five inboxes, Zapier can post the events that need a response into a Slack or Microsoft Teams channel, with the key details in one line. I keep these few and specific; an alert channel that fires constantly is muted within a week.
AI steps with someone signing off
Zapier can pass text to the main AI model providers to summarise an enquiry, pull details out of an email or draft a reply. I set these up with a human in the loop: the draft waits for a named person to approve it, and nothing goes to a customer automatically.
When another platform fits better
Choosing the tool comes before building in it, and Zapier is not always the answer. The glossary entry on Zapier and Make sets out the main differences. My usual reasoning runs like this:
- Make tends to suit processes with many branches or large batches of items, where Zapier’s task count would climb.
- n8n is worth considering when customer data must stay on servers you control, or when run volumes are high.
- Built-in workflows in HubSpot, Klaviyo or your booking system are simpler when the whole process lives in one platform.
- No automation yet is the honest answer when the process changes every few weeks. Run it by hand until it settles.
How a build runs
- Walk through the process. We go through it together and I write down the trigger, each app involved, who does what and what should happen if a step fails.
- Set up ownership. The Zapier account is in your company’s name and billed to you. Where your plan allows, I work in a shared team workspace, and app connections use shared business logins rather than one person’s account.
- Build with messy data. I test each Zap against the records you really get: missing surnames, “Ltd” and “Limited” for the same company, postcodes in lower case, enquiries submitted twice.
- Plan for failure. Error notifications go to an inbox someone watches, and Zaps that matter get a fallback so a failed step is spotted and rerun rather than lost.
- Watch the first live runs. Once the Zaps are live, I review Zap history, adjust filters and check task usage against the estimate.
- Hand over. A recorded walkthrough for whoever will own the Zaps, plus the documentation listed below.
Problems I find in existing Zapier accounts
- Zaps built on a former employee’s or freelancer’s personal login, so the business does not control them.
- Dozens of Zaps named “Untitled Zap” or “Copy of”, some switched off, some duplicating each other’s work.
- Zaps that write the same contact to the CRM twice because two triggers fire on one enquiry.
- Errors emailed to an address nobody checks. Zapier can switch off a Zap that keeps failing, and nobody notices until leads stop arriving.
- Personal data copied into spreadsheets and kept indefinitely. UK GDPR expects you to hold only what a process needs and only for as long as it needs it.
- Formatter and filter logic duplicated across several Zaps, so a change has to be made in five places.
Zapier is a US company, so personal data that passes through it is generally processed outside the UK. Its data processing agreement explains how that is covered, and it belongs in your records alongside the Zaps.
What you receive
- Working Zaps in your account, named consistently and grouped into folders by process.
- A one-page note for each Zap: what starts it, what it changes, where errors go, how to pause it and how to rerun a failed task.
- An estimate of monthly task usage, so you can pick a plan with headroom.
- A list of the personal data each Zap moves and where it is stored, for your own records.
Pricing
You will pay two separate bills. Your Zapier subscription goes directly to Zapier and is set by the number of tasks you use each month and the features you need. Zapier publishes its current plans, prices and task allowances on its own pricing page, and they change from time to time. Before you choose a plan, I count the steps and expected runs for each Zap so the allowance fits.
The second is my fee for planning and building. Each quote is written in GBP after a free first call, once the scope is clear, and agreed in writing before any work starts. I do not resell Zapier or hold your account on my side, so if we stop working together you keep every Zap and I remove my access.
Next step
Tell me which process you want automated, the apps involved and roughly how many records go through it each month. If you already run Zaps, list what they are supposed to do and what keeps going wrong. Book a free 30-minute call and I will tell you whether Zapier is the right fit, or which tool I would use instead.