Workflow automation
Workflow automation means letting recurring processes between applications run automatically — such as creating invoices, transferring data or sending notifications — instead of doing them by hand.
Typical tools are n8n and Make: they connect applications through triggers and actions, such as “new order in the shop” → “create invoice, print shipping label, notify customer”. For more complex cases, custom services are added.
The benefit shows in tasks that are frequent, repetitive and error-prone. It is important to clarify processes first and plan for failure cases — otherwise you only automate the chaos.
Practical examples: at Candli and Zarrillo, invoices, delivery notes and DHL shipping labels are created automatically; at agroplanta the newsletter is connected to the website with double opt-in and an automatic reminder.
What to look out for
- Collect processes that are frequent, repetitive and error-prone — automation pays off there first.
- Write the process down and simplify it before automating.
- Define for every workflow who is notified when something goes wrong.
- Set up access to connected systems with dedicated, restricted accounts.
- Document automations so they remain understandable without their creator.
Common mistakes
- A chaotic process is automated — and now produces errors faster.
- Automations fail unnoticed because nobody receives error messages.
- Dozens of individual workflows without an overview of who built what.
Frequently asked questions
Both connect applications through triggers and actions. n8n can also be self-hosted, for example on your own servers in Germany; Make is a pure cloud service with a very large number of ready-made connectors. The choice depends on data protection requirements, complexity and existing systems.
Typical ones are invoicing and shipping processes, transferring website enquiries into the CRM, team notifications and recurring reports.
More in our article: Automating processes with make.com and n8n: where the real leverage is