Berlin · SMEs · workflow automation
Automating workflows with n8n — from Berlin.
Most manual office work is handover: a figure from an email into a form, a receipt from an inbox into accounting, an enquiry from the contact form into the CRM. n8n chains those steps visibly and traceably — on a server you control, without per-operation billing.
Built and run by one person. No handover to a partner network.
Location
Close enough to watch it running
Automation rarely fails on the technology and almost always on the fact that nobody knows exactly how the process runs today — including the exceptions written down nowhere. So the work starts at your desk: sitting alongside once and watching the process go through by hand. In Berlin that is an appointment, not a travel expense question.
Techlogia — Jaciel A. Acea RuizPrinzenallee 38
13359 Berlin
Where we work
Recording the process happens on site in Berlin and Brandenburg. Building, integration and operation then run remotely — across Germany, as well as Austria and Switzerland where the recording can be done by screen share.
What actually pays off
Four processes that almost always return the effort
Not every manual step deserves automating. It pays where the same handover happens often, where typing errors get expensive, and where waiting time appears because somebody only checks the inbox on Monday.
Receipts from the inbox into accounting
Incoming invoices are recognised, read out, assigned to the right case and passed on. What is unambiguous runs through; what is not lands on a review pile instead of being quietly booked wrong.
Enquiries from the form into the CRM
Every enquiry produces the same record, the same assignment and the same acknowledgement — weekends included. Follow-up deadlines are carried along, so an enquiry is not lost simply because it sat beneath twenty other mails.
Quote, order and invoice as one chain
Details are captured once and travel through the stations rather than being retyped at each one. The time saved is one thing; the address and line items reading the same everywhere at the end is the other.
A bridge between systems that do not talk
Inventory management, time tracking, online shop, tax adviser — each can export, none knows the other. n8n sits in between and translates, without any of those systems having to be replaced.
How we work
How an automation comes about
- 01
Write the process down
Sit alongside once and walk the process through by hand. That is where the exceptions surface that later trip up every automation — and that appear in no process description.
- 02
Set the narrowest useful cut
One workflow that runs all the way through, rather than five half ones. What it does and explicitly does not do is written down beforehand — otherwise scope grows during the build and nobody can say when it is finished.
- 03
Build and integrate
Implementation with n8n, connected to your existing systems through their interfaces. Credentials are stored encrypted, not inside the workflow itself — otherwise they travel out with the first export.
- 04
Hand over and monitor
You get the workflow, a short briefing and alerting that speaks up when it stops. Failed runs stay visible and can be replayed once the cause is fixed.
What it costs
Fixed prices for the parts an automation is made of
Automations consist of parts that can be priced individually: a container for processing, an interface to an existing system, a command-line tool. What your project costs in total follows from how many of those parts it needs.
Container
Docker Container for Data Processing
Custom pipeline for your data — cron jobs, webhooks, REST API, deployable on any Docker host. ETL, scraping, aggregation.
from €1,490
Backend
API Backend
Production-ready REST API with auth, rate limiting, OpenAPI docs — as backbone for your app or third parties.
from €1,890
CLI Tool
CLI Tool / Command Line
Command-line tool for power users and automation — Python, Go or Rust, cross-platform, pipe-friendly.
from €1,290
Net, plus VAT. Running n8n itself comes on top and depends on whether it runs on a new server or one you already have. To place the effort in advance, the configurator gives a guide figure.
Automation is one part of what sits under DevOps — alongside delivery pipelines, container operations and backups. The technical depth on that is on the service page.
See DevOps & automation →Frequently asked
Questions we get asked a lot
What is n8n — and why not Zapier or Make?
n8n is a workflow engine you can run yourself. The decisive difference from hosted services: the data flowing through your processes passes over a server you control, and billing does not depend on the number of operations. We still use Make where it fits better — the choice follows the use case, not a preference.
Can we change the workflows ourselves later?
That is exactly what n8n is built for. Workflows are visible chains of building blocks, not lines of code — your team can swap a recipient or add a condition without asking us. For anything beyond that, the door back to us stays open.
Where does it run — with you or with us?
By default on a server in Germany that we set up for you. If you have your own infrastructure, it runs there. Both work, and moving between them is a relocation, not a rebuild.
What happens if a workflow stops at night?
Monitoring reports it, not your customer. Every setup includes alerting by mail plus a second channel, so a silent failure does not look like calm. Failed runs stay visible and can be replayed once the cause is fixed.
How much work is left on our side?
Once the workflows are in place, little: you look at the logs when monitoring calls. Realistically one to two hours a month for review and small adjustments, plus occasional peaks when a connected system is rebuilt on its own.
Get in Touch
Have a project?
Let's bring your idea to life together. We're happy to advise you with no obligation.