There’s a kind of work nobody likes but someone always ends up doing: copying a piece of data from one place and pasting it into another. The order that arrives by email and has to go into the spreadsheet. The form lead that then goes into the CRM by hand. The number that gets moved from one tool to another every Monday. It’s invisible work, dull, and on top of that it’s where most errors creep in. The automations I build handle exactly that: they connect your apps so the information travels on its own, without anyone having to touch it.

What is an automation?

An automation is a connection between two or more of your tools that fires on its own when something happens. An order comes into the store → the invoice is created, the warehouse is notified, and the customer gets their tracking. Someone fills out a form → it’s logged in the CRM, a welcome email goes out, and you get a notification. You define the “when this happens, do that,” and the system repeats it a thousand times without getting tired or making mistakes.

It looks like an AI agent but it isn’t the same thing, and the difference matters so you don’t overpay. An AI agent decides: it reads an ambiguous request, works out what the person wants, and picks the path. An automation executes: it follows a fixed route you already defined. If your problem is “when A happens, do B” with no ambiguity, you don’t need AI: you need an automation, which is simpler, cheaper, and more predictable. Half the times someone asks me for “an agent,” what actually solves their problem is a good automation.

And Zapier? It’s the best-known version of this, and for tiny cases it’s perfect. But it charges per step, gets expensive the moment the flow grows, and your data always passes through their servers. I work with n8n for reasons I get into below, but the core idea is the same: getting your apps to talk to each other on their own.

How it works under the hood

Every automation has three parts. A trigger (the “when”): a new row in a spreadsheet, an incoming email, a form submission, a time of day. One or more actions (the “what”): send a message, create a record, calculate something, fetch a value from another app. And the logic that ties them together: “if the amount is over X, notify the owner; otherwise carry on.”

I build it all in n8n, a visual platform where each step is a block that connects to the next. It’s not lines of code: it looks more like a flowchart, and that has a concrete upside for you, because you can see what your automation does at a glance instead of trusting a black box. It plugs into almost everything you already use: Gmail, Sheets, WhatsApp, Calendar, Airtable, HubSpot, Stripe, and hundreds more. I don’t ask you to switch tools; I connect the ones you already have.

What it does for your day to day

The pattern is always the same: if there’s a repetitive task that a person does today by moving data between systems, it can probably be automated.

Moving data between systems. The classic. Orders that go from the store to the spreadsheet, leads that go from the form to the CRM, invoices copied to the accountant. Each of those manual hops is lost time and a chance for a typo. Manual data entry runs a typical error rate of 1 to 4% (peer-reviewed literature). Automated, the data travels just the same at three in the morning as it does on a Monday at nine.

Automatic reports and summaries. Instead of building the same report every week, the system gathers the numbers from wherever they live, sorts them, and sends you the summary ready by email or WhatsApp. Same with alerts: “tell me the moment an important client hasn’t paid,” “send me the day’s sales at 8pm.”

Onboarding and follow-ups. When a new client comes in, the whole sequence fires on its own: welcome email, CRM entry, folder created, reminder after three days. You define it once and it stops depending on someone remembering.

Reconciliation and checks. Cross-checking what one tool says against another —payments against invoices, stock against sales— is tedious and easy to get wrong. An automation does it every night and flags only what doesn’t line up.

The common thread is that you stop being the cable between your own tools. And beyond time, that gives you precision: an automation doesn’t get distracted, doesn’t skip a row, and doesn’t mistype a number.

What I build them with, and why

I choose n8n for the same reasons as everything I do: when the project ends, the flow is yours, not the platform’s. n8n is open source and can run on your own server, so your data doesn’t have to pass through an outside company, which matters if you handle sensitive client info, payments, or records. It charges per execution, not per step, so a fifteen-block flow doesn’t cost you fifteen times more. And behind it is a European company backed by serious funds, one that won’t vanish next year.

When is n8n not the right call? If your case is two steps and a single integration —“when an email with an attachment arrives, save it to Drive”— Zapier handles it in ten minutes and you’re done. I’ll be the first to tell you. n8n shines when there’s conditional logic, sensitive data, several systems, or volume. Which is where nearly every real small-business case lives.

How long it takes to ship

A simple automation (one trigger, two or three actions, no odd cases) is usually ready in a few days. One that connects several systems with conditional logic, one to two weeks. The bigger ones, orchestrating half an operation with error handling and retries, can take longer.

What’s almost never the bottleneck is building the flow. What stretches things out is getting access to each tool, cleaning data that comes in dirty, and discovering the edge cases nobody mentioned in the first conversation (“oh, but if the client is from abroad, the format changes”). That’s why I always start with a short diagnostic: I’d rather map the real flow properly before promising timelines.

A real example

A business that takes bookings through its website lived with the same bottleneck: every booking that came in had to be confirmed by hand over WhatsApp, added to the calendar, and passed to the team. Multiplied by dozens a day, it was nearly a full-time person acting as a switchboard between the website and the rest of the tools.

Now a booking comes in and everything fires on its own: confirmation to the customer over WhatsApp, slot created in the calendar, the team notified with the details. The person who used to be the cable now spends their time looking after the clients already inside. For a sense of the scale this can reach: Delivery Hero managed to shed around two hundred hours a month with a single n8n flow. A small business doesn’t play in that league, but the principle scales down just as well.

Frequently asked questions

How is this different from an AI agent?

An automation follows a fixed route you defined; an agent decides its path based on context. For “when A happens, do B” with no ambiguity, the automation is simpler and cheaper. When something has to be interpreted (a natural-language request, a decision that changes case by case), that’s where AI comes in. A lot of projects end up being a mix: automation for the mechanical parts, a touch of AI only where it’s genuinely needed.

Do I need to change the tools I use?

No. The whole point is to connect what you already have. n8n integrates with hundreds of apps, and for the ones without a direct integration there’s almost always a way in (their API). The goal is to get your current stack talking on its own, not to replace it.

What happens if something fails midway?

It’s designed for that. A well-built automation has error handling: if an app doesn’t respond, it retries; if something stays wrong, it tells you instead of failing in silence. For sensitive steps (a charge, an email to a key client), it can ask for your confirmation before running. Nothing is left to chance.

Is it safe with my data?

Yes, and it’s one of the reasons I use n8n. Running on your own infrastructure, the data doesn’t leave to a third-party platform. You keep control of where everything lives.

Do I own the automation?

Yes. n8n is open source, the flow stays documented, and the data is yours. If you ever part ways with me, you take it all with you, still running. It’s the difference between renting a tool and building something of your own.

If you’ve got a repetitive task eating up your time every week, tell me about it and we’ll see if it can be automated. The first twenty-minute call is free. You can also ask Kyn, the site’s AI chatbot, to help you think through where to start.