Module 4Academy

Automating with n8n, Make and Power Automate

Triggers, actions and conditions. Which platform fits which work, and how an automation survives the week.

Automating with n8n, Make and Power Automate is a training day in which the team learns how an automation is built: a trigger, the steps and the check. The team builds one working chain on one of the three platforms, and learns which choice fits which work, including questions about data processing and management.

After this module the team can
  • 01The team builds one working chain with a trigger, at least two steps and a condition
  • 02Each chain gets error handling, a log entry and a notification to a person
  • 03For a given task the team can explain which platform fits, and why, including data processing
  • 04The team has a checklist for putting an automation into production
Agenda
  1. 01

    Trigger, action, condition

    The building blocks of every automation. We build a chain without AI first, so the logic is visible before a model enters.

  2. 02

    Platforms side by side

    n8n, Make and Power Automate: how they work, what they cost and where the data sits. We compare on the participants’ tasks, not on the vendor’s presentation.

  3. 03

    Errors and management

    What happens when a step fails, how to avoid double processing, and who watches the chain when its maker has left.

  4. 04

    Going live

    The production checklist: test data, rights, logging, a fallback and an owner. Then we switch on the first chain.

An automation is a chain, not a miracle

Every automation has three parts. There is a trigger: something happens, such as an email arriving, a form being filled in or a file appearing in a folder. There are actions: the data is read, converted, stored somewhere or sent. And there is a condition that decides whether a step runs. Whoever knows those three can read and build almost any chain.

The tempting misunderstanding is that an AI step is the heart of the chain. In practice the logic is the heart and the model is one step. That is why this training first builds a chain without AI. Only when it runs reliably do we place the model where text must be read or written.

Three platforms, three ways of working

n8n has a cloud version with servers in Frankfurt according to the vendor, and a version you can self-host. The licence of the self-hosted version allows internal use and does not allow selling the service to third parties. Make works with a visual designer and scenarios with branches, and charges in credits. Power Automate sits inside Microsoft 365; the EU Data Boundary requires a tenant and a billing address in the EU, and premium connectors are paid separately.

Which platform fits depends on where the work arrives. If the work sits in Microsoft 365 and Dynamics, Power Automate is the obvious choice. If you have a technical team that wants to self-host, n8n is the natural choice. If you want to build visual scenarios with many branches, Make fits. We compare the three on the participants’ tasks, and show the prices the vendor publishes on the day.

Error handling: the part everyone skips

A chain that works once is a demo. A chain that works every day has error handling. What happens when the source does not respond, when an amount does not fit, or when a step runs twice because the trigger fired twice? The training gives each chain an answer to those three questions: a retry with a maximum, a check against double processing, and a notification to a person for anything that does not resolve itself.

With that comes a log entry. Anyone who later wants to know what happened to an order must be able to find it in a log. That sounds dull, but it is the reason an automation is still trusted after half a year.

Where the model belongs in the chain

A language model is good at reading free text and drafting a proposal: a summary of an email, a draft reply, an extraction from a quote. It is less good at decisions that must rest on a number alone. So we place the model only where it reads or writes text, and let the rest of the chain do the work, with a check where the result lands.

That is also why the production checklist includes a human approval for every action with consequences outside the system, such as a payment or a client email that goes out.

The production checklist

Before a chain goes live, the team works through the list: was test data used that resembles the real situation; are the rights as small as they can be; is there logging; is there a fallback if the system fails; and is there one person who watches the chain. The last question matters most. An automation without an owner breaks silently, and nobody notices until the following month.

Frequently asked questions

  • Which platform do you recommend?

    That depends on where the work sits, who manages it and what data is in it. The comparisons at /compare/zapier-vs-make-vs-n8n/ and /compare/power-automate-vs-zapier/ show the sources and check dates. We choose with you, not for you.

  • Can n8n be used for free in a company?

    The self-hosted Community Edition is free under the Sustainable Use License, for internal and non-commercial use. If you deliver the automation as a service to third parties, that is a different case. Read the licence before you choose.

  • Does this replace an ERP link?

    Sometimes, often not. An ERP link that must be reliable belongs to a build with a blueprint. An automation is good for the work around it: email, files, notifications and small links.

Which team needs this module?

For up to 12 participants €3,950 excl. VAT. In the conversation we say whether the module fits, or whether a build day or the adoption programme is better.