Process automation in a small business: the basics

Process automation means that a program carries out a fixed sequence between your programs by itself as soon as a defined event occurs, for example an enquiry through your contact form. Nobody types data in again, and a person only checks the result. Suitable are tasks that occur often, follow the same rules and whose data is already digital.

Trigger, steps, connections

Every process, called a workflow in technical language, has three parts. The trigger starts it, for instance a completed form or a fixed time of day. The steps do something, such as creating an entry or sending a message. The connections give the tool access to your programs so that it may read and write there. n8n calls the stored login details for this credentials, and Microsoft calls the connections connectors.

n8n describes a workflow as a collection of connected building blocks that automate a process. It starts when a trigger condition occurs and then runs one step after another. Zapier, Make and Power Automate follow the same basic pattern, but they name it differently and bill in different units:

Tool	Whole process	Trigger	Step	Billed by
n8n	Workflow	Trigger	Node	Execution, meaning one complete run
Zapier	Zap	Trigger	Action	Task, meaning one successful action step
Make	Scenario	Trigger module	Module	Credit, for most apps 1 operation equals 1 credit
Power Automate	Cloud flow	Trigger	Action	Licence per user or per automation

The way the trigger learns about a new event also differs. A polling trigger checks at intervals whether anything new has arrived. Make checks every 15 minutes by default, and with Zapier the interval depends on plan and app. An instant trigger, by contrast, is notified by the other program. Whether a program offers a trigger at all cannot be taken for granted: n8n states explicitly that not every integration has one.

The four tools without a verdict

I do not recommend a product here. Which one fits depends on your programs, your data and your willingness to run something yourself.

Zapier and Make: in the help pages I read, both vendors describe set-up in their own editor (Zap editor, Scenario Builder). I found no operation on your own server there. On that evidence, the data of your process runs through the vendor’s service. Which data may do so is a data protection question. Zapier counts only successful action steps as tasks, and triggers do not count. According to Zapier, multi-step Zaps with more than one action are available only on paid plans. Make bills in credits, and every run of a module counts as an operation. According to Make’s help, that includes the trigger: a polling trigger uses one operation per check, however much new data it finds.

n8n: the source code is on GitHub, and use is subject to the Sustainable Use License. By its wording it permits use only for your own internal business purposes or for non-commercial use. According to the vendor’s FAQ, the self-hosted version is free as long as workflows are created or changed only by people in your organisation. There is also n8n Cloud from the vendor. According to the pricing page, the Starter plan costs 20 € a month with annual payment and includes 2,500 executions, and Pro costs 50 € and includes 10,000 (vendor statements, as of 13.11.2026; the page does not say whether net or gross). Anyone who self-hosts must also update it themselves. How often that may be necessary is shown by the vendor’s security notices on GitHub: on 28 October and 13 November 2026 alone, 16 notices appeared, 4 of them rated High and 12 rated Moderate.

Power Automate: Microsoft calls the processes cloud flows. There are also desktop flows, which imitate keyboard and mouse input on a workstation computer. Licensing is per user or per automation. According to Microsoft, other Microsoft 365 licences include a limited part of the functions. What your contract includes is stated in your licence.

When a process is suitable

The following features are the author’s assessment. No vendor specifies them, and I have not measured them:

• The task occurs often enough that doing it by hand costs noticeable time.
• It almost always runs the same way, and exceptions are rare and recognisable.
• The data is already digital, in programs that can be connected.
• A mistake gets noticed and can be corrected.
• One person remains responsible for checking results and making decisions.

If one of these is missing, it usually pays to sort out the task itself first. A process does not turn an unclear task into a clear one, it merely repeats faster what it is told. Where there are many exceptions, they end up with the office and cost more time there than before.

An example with invented data

An invented trades business receives 40 enquiries a month through its contact form. By hand, entering each enquiry in the customer list takes 3 minutes, the confirmation of receipt 2 minutes and the notice to the office 1 minute. That makes 6 minutes per enquiry, altogether 40 times 6, so 240 minutes or 4 hours a month. All values are assumptions for this example.

1. Trigger: form An enquiry arrives through the contact form
2. Entry in customer list Name, phone and request go into the spreadsheet
3. Send confirmation The customer gets a standard email confirming receipt
4. Notice to the office Message to the office manager with a link to the entry
5. Office decides Call back, appointment or quotation: a person decides

Text version of the graphic

• 1. Trigger: form: An enquiry arrives through the contact form
• 2. Entry in customer list: Name, phone and request go into the spreadsheet
• 3. Send confirmation: The customer gets a standard email confirming receipt
• 4. Notice to the office: Message to the office manager with a link to the entry
• 5. Office decides: Call back, appointment or quotation: a person decides

The process takes over these three steps. The office still looks at every enquiry, say 1 minute per case, so 40 minutes a month. What remains is 240 minus 40, so 200 minutes or 3 hours 20 minutes that no longer have to be spent.

by handwith workflow

• Entry in customer list40 × 3 min

  by hand 120 min/month
  with workflow 0 min/month

• Confirmation of receipt40 × 2 min

  by hand 80 min/month
  with workflow 0 min/month

• Notice to the office40 × 1 min

  by hand 40 min/month
  with workflow 0 min/month

• Office looks at every enquiry40 × 1 min, stays manual

  by hand 0 min/month
  with workflow 40 min/month

Source: Worked example with invented data, all values are assumptions

Text version of the graphic

• Entry in customer list: by hand 120 min/month, with workflow 0 min/month (40 × 3 min)
• Confirmation of receipt: by hand 80 min/month, with workflow 0 min/month (40 × 2 min)
• Notice to the office: by hand 40 min/month, with workflow 0 min/month (40 × 1 min)
• Office looks at every enquiry: by hand 0 min/month, with workflow 40 min/month (40 × 1 min, stays manual)
• Source: Worked example with invented data, all values are assumptions

Set-up, upkeep and checking take time themselves, and you set that against it. With only 5 enquiries a month it would be 5 times 5 minutes, so 25 minutes. Whether set-up and upkeep pay off is then doubtful. The task must therefore not only run, it must occur often enough.

Billing also depends on the unit. The process has three action steps. With Zapier that is 3 tasks per enquiry, so 40 times 3, or 120 tasks a month, provided all steps succeed. With n8n it is one execution per enquiry, so 40 a month, because according to the pricing page the whole run counts regardless of the number of steps. With Make, the three modules give 40 times 3, so 120 operations. The trigger’s operations come on top. How many depends on how often it checks, and cannot be put in figures without your settings.

Limits

Prices, plans and features change. Zapier itself writes in its help that from 1 December 2026 Next Gen Zaps and the Zapier SDK will also use tasks. All statements here apply to November 2026.

Not every task is suitable, and a process without monitoring fails unnoticed. Which data may go into which tool, you clarify with your data protection officer. Questions about the licence in an individual case are for your legal adviser. The vendor also names its own address for licence enquiries in its FAQ.

What you can do now

1. Write down three tasks for which you transfer data from one program to another every week.
2. For one of them, count the cases for a month and time the minutes per case. Calculate cases times minutes.
3. Look in a tool’s list of integrations to see whether your programs offer a trigger and the steps you need.
4. Before any process that handles personal data, clarify who may process it and which contract belongs with it.