A workflow describes who does what in which order. An automation hands some of those steps to a machine.
01 In short
What is a workflow? A workflow is a sequence: a trigger, a fixed series of steps and a result. Every business has workflows, even if nobody has ever written them down. Workflow automation means that individual steps within it run without anyone lifting a finger. So the automation is not the workflow itself but a property of its steps. Anyone who wants to automate therefore describes the workflow first, then decides step by step what the machine takes over and what stays with people.
02 What a workflow is
Every workflow has the same three parts.
- A trigger. An e-mail arrives, a form is submitted, a deadline approaches, a month ends.
- Steps in a fixed order. Read, assign, check, enter, file, notify. Each step has an input and a result.
- An end. The case is done, filed or handed on to the next person.
An example from property management: an invoice arrives by e-mail. Someone opens the PDF, finds the property, checks the amount against the order, puts the invoice forward for approval, books it and files it. That is a workflow, whether it lives on paper, in people's heads or in software.
03 What workflow automation is
An automation takes over individual steps of a workflow that a person used to do by hand. In the example: fetching the invoice from the inbox, reading the invoice data, matching the property, preparing the entry in accounting, saving the PDF in the document store.
Not every step has to run automatically for the automation to pay off. Approving the invoice stays with the person responsible for it. We automate the recurring work, not the judgement.
04 Why you describe the workflow first
A workflow that only exists in people's heads has gaps. Who decides when the amount does not match the order? Where does an invoice without a property go? Who covers during holidays? As long as a person does the work, they catch these gaps without thinking about it. A machine cannot.
That is why every project starts by describing today's workflow: trigger, steps, exceptions, responsibilities. Often the description alone shows that a step is unnecessary or done twice. How this runs in a project is described in How a first workflow goes live in four weeks.
05 What automates well
A step is a good candidate if it happens often, follows a rule that can be written down, and its inputs arrive in a similar form. Typical examples:
- Transferring data from one system to another
- Sorting and assigning e-mails and documents
- Reading fields from invoices, delivery notes or forms
- Watching deadlines and sending reminders
- Compiling reports from several sources
Whether a whole process is worth it is checked by four tests in How to tell whether a process is worth automating.
06 What stays with people
Approvals, negotiations, decisions that need discretion and anything someone has to answer for. An automated workflow prepares these decisions, it does not make them. It puts the invoice forward for approval with the fields already read, it does not pay it. It drafts the reply to the tenant, it does not send it unread.
07 Workflow automation with AI: two kinds of step
Most steps in a workflow are ordinary logic: if the amount is above a limit, the invoice goes to management. These rules are checkable and always give the same result for the same input.
A language model is only needed where a step has to understand language or documents, for example sorting an informal e-mail or reading an invoice whose layout is different every time. Exactly where that line runs is described in Where the AI sits in a workflow — and where it does not.
08 Workflow, automation, agent
Three terms that are often mixed up:
| Term | What it is | Who decides the steps |
|---|---|---|
| Workflow | The sequence itself, with or without software | The business |
| Automation | Steps of the workflow run without anyone acting | Fixed in advance |
| AI agent | A model chooses its own next steps | The model, within its tools |
For most office processes the middle row is enough. Why is explained in What an AI agent is, and when you do not need one.
09 What a workflow is built with
We build workflows between the systems a business already has: e-mail and calendar, CRM, accounting and ERP, document storage and DMS. Those systems become one continuous process: captured, assigned, checked, in sync, followed up. Our tool for this is usually n8n, described in What is n8n. Which workflows these are in your industry is shown under Industries.
10 Frequently asked questions
Do I need new software for a workflow?
No. The workflow already exists; today it runs by hand. It is automated between the systems you already use.
Is every automation AI?
No. Most automated steps are fixed rules. AI only comes in where language or documents have to be understood.
What software does workflow automation need?
A tool that connects systems and runs the steps, such as n8n, Make or Power Automate. The comparison is in n8n, Make and Power Automate. More important than the tool is the description of the workflow.
How big should the first automated workflow be?
Small enough to go live within a few weeks, and frequent enough that the time saved can be measured. What such a workflow costs and saves is worked through in What a workflow costs and what it saves.