Why do German companies choose n8n over Zapier or Make?
Three reasons come up in almost every conversation: n8n can be self-hosted, it comes from a Berlin company, and it handles complex logic without per-step pricing on your own server. For firms whose data protection officer asks where every record goes, being able to say "on our server in Frankfurt" ends a lot of discussions.
n8n describes itself as based in Berlin, and its hosted service, n8n Cloud, runs on Microsoft Azure infrastructure in the European Union according to its security page. That gives German buyers two EU-based paths: rent n8n as a service, or run the same software on a machine they control.
The second reason is how workflows are built. Zapier and Make are excellent for linear "when this, do that" flows. n8n is closer to a visual programming tool: branches, loops, sub-workflows, code nodes in JavaScript or Python, and an HTTP Request node that talks to any API with documentation. German SMEs rarely use only mainstream apps; they use lexoffice, weclapp, JTL, a regional bank, a DATEV export, an old ERP with a CSV interface. n8n reaches all of them.
The third reason is cost behaviour. On a self-hosted instance you pay for the server and any licence tier you choose, not for each step a workflow executes. For high-volume flows such as order syncing, that changes the arithmetic considerably. That is also why the n8n automation agency market has grown in Germany: the tool rewards careful setup.
What does an n8n automation agency actually deliver?
An n8n automation agency delivers four things: a working instance, workflows that survive real-world errors, documentation your team can follow, and ongoing care. The workflows get the attention, but the other three decide whether automation still works a year later.
The instance is the foundation: n8n with a proper database, HTTPS, user accounts, backups and an update routine. The workflows are the visible part: each one has a trigger, steps, error paths and a clear owner in your company. Documentation means a runbook per workflow explaining what it does, what can go wrong and who to call. Care means someone watches failed executions, updates n8n and fixes things when an API changes.
We work as three freelance developers rather than a large team, which suits this kind of work: the same people who build your workflows also maintain them, so nobody has to rediscover why a node was configured the way it was. When you hire any n8n automation agency, ask who will be looking at failed runs in month eight; the answer tells you more than the portfolio.
n8n Cloud or self-hosted: which suits a German company?
Choose n8n Cloud if you want no server to manage and are comfortable with n8n as a processor under its terms. Choose self-hosting if your data protection officer wants data on infrastructure you control, if you need to reach systems inside your company network, or if your volume makes execution-based pricing expensive.
n8n Cloud is run by n8n on Azure in the EU, and n8n states that it holds SOC 2 compliance with annual independent audits. You sign up, accept its data processing terms and start building. Updates, backups and uptime are n8n's job. The limits are the plan limits and the fact that anything inside your firewall needs a secure route in.
Self-hosting means running n8n yourself, typically in Docker with PostgreSQL, on a server at a German or EU hosting provider, in an EU region of a large cloud such as AWS Frankfurt, or on-premises. You gain control over location, network access and retention; you take on patching, backups and monitoring, or you pay someone to do them.
A middle path works well for many Mittelstand firms: self-host in your own EU cloud account, and let a maintenance retainer cover the operational chores. That is the setup we build most often, and the table further down compares all three options side by side. Whichever you choose, the n8n automation agency you hire should put the instance in your name, not theirs.
Is n8n free for commercial use under the Sustainable Use License?
For internal automation in your own company, yes. The Sustainable Use License states that you may use or modify the software "only for your own internal business purposes or for non-commercial or personal use". Automating your own sales, accounting, HR and support processes falls within that.
What the licence restricts is selling n8n itself, or a product whose value comes substantially from n8n, to others. You may not distribute it except free of charge for non-commercial purposes, and you may not remove n8n's licence or copyright notices. n8n's own documentation describes examples of allowed and restricted use and gives a contact address for edge cases; if you plan to embed n8n in a product you sell, ask n8n directly and involve your lawyer.
Two practical points follow. First, when we build workflows for your company on your instance, you are the one using n8n for internal purposes, and we provide consulting and build services around it, which n8n said openly, when it announced the licence, that others are free to offer. Second, some features sit in paid tiers. Before recommending a tier we check n8n's current plan page against the features you need, such as single sign-on or advanced permissions, rather than assuming.
The full licence text is in the n8n repository; reading it takes five minutes and is worth doing. This is not legal advice, and a genuinely unclear use case belongs with your counsel.
How does an n8n automation agency set up n8n to suit GDPR?
The main GDPR levers in n8n are where it runs, how long it keeps execution data, who can see that data and how credentials are protected. A careful setup handles all four before the first live workflow.
Location. Self-hosted n8n runs wherever you put it; for German clients that is an EU server. n8n Cloud runs in the EU. Either way, every connected service (your CRM, an AI model, an email provider) is its own data flow with its own location and AVV, so the list of services per workflow belongs in your processing records.
Execution data. n8n stores the input and output of workflow runs so you can debug them. That is useful and also a copy of personal data. We configure pruning so execution data is deleted after a period your data protection officer agrees, save full data only for failed runs where needed, and avoid logging fields that are not required.
Access. Named user accounts, no shared admin login, and permissions limited to the workflows each person needs. Access for our developers is through accounts you can disable at any time.
Credentials. Covered in its own section below. The build supports your obligations; whether the setup is sufficient for your organisation is confirmed by your own data protection officer or counsel. For the website side of the same topic, see our GDPR compliant website guide.
Which German business tools can n8n connect to?
An n8n automation agency can reach almost all of them, because anything with an API can be reached through n8n's HTTP Request node even when no dedicated node exists. The question is effort, not possibility.
lexoffice / Lexware Office
A documented REST API for contacts, invoices, vouchers and files. Typical flows create invoices from shop orders or upload receipts from email.
sevDesk
A public API plus community-built n8n nodes. Community nodes save time but need checking before use, because they are maintained by third parties.
Personio
An API for employee and absence data. Onboarding and offboarding flows are common, and they involve employee data, so works council and retention questions come first.
Shopware
The Admin API and webhooks let n8n react to orders, customers and stock changes and write back status updates.
DATEV
Most SMEs send data to their tax adviser as DATEV-format booking exports; n8n can assemble those files from approved records, with the account mapping agreed with the Steuerberater.
Microsoft 365 and Google Workspace
Outlook, Teams, SharePoint, Gmail and Sheets all have built-in n8n nodes, which makes notifications and approvals easy to place where staff already work.
For deeper DATEV work, including the online APIs and their access requirements, see the DATEV API integration page.
How should n8n workflows handle errors?
Any n8n automation agency worth hiring assumes every external system will fail at some point and designs for it. An n8n workflow that works in testing but has no error path will eventually drop an order or an invoice without anyone noticing.
We use four layers. Retries on nodes that call external APIs, with waiting times, because many failures are brief. Validation before writing anything: required fields present, amounts plausible, IDs found. Error workflows: n8n lets you assign a separate workflow that runs when another fails; ours posts a clear message to Teams or email with the workflow name, the record involved and a link to the failed execution. A catch-up path: failed items are written to a queue or table so they can be re-run once the cause is fixed, instead of being lost.
Idempotency matters too. If a shop order is processed twice because of a retry, it must not create two invoices. We use the source system's IDs as keys and check before creating records.
Finally, someone has to read the alerts. Part of every handover is agreeing who in your company receives them, and what the maintenance retainer covers. An n8n automation agency that sends alerts only to itself leaves you blind when the relationship ends.
How does an n8n automation agency store credentials and back up n8n?
n8n encrypts stored credentials with an encryption key, so the key is as important as the database. Lose the key and the credentials cannot be recovered; leak it together with a database copy and they can be read.
On self-hosted instances we set the encryption key explicitly, store it in your password manager or secrets store, and keep it separate from database backups. API keys used by workflows are created as dedicated service accounts in each connected system with the narrowest permissions that work: an accounting key that can create invoices but not delete them, for example. When an employee or contractor leaves, the relevant credentials are rotated.
Backups cover three things: the PostgreSQL database (workflows, credentials, execution history), the encryption key, and the workflow JSON exports, which we also keep in your Git repository so every change is versioned. A backup nobody has restored is only a hope, so we test a restore to a separate instance during handover.
On n8n Cloud, backups and infrastructure security are n8n's job, but exporting workflows to your repository is still wise, because it gives you a readable history and a way to move if you ever self-host.
How much does an n8n automation agency cost?
With BtechWaleTech, a workflow build starts at US$600 and a typical project runs 2–4 weeks; maintenance starts from US$120/mo a month once the two free months end. Rates at other providers vary widely, so compare the number of workflows, the error handling and the hosting work included, not a headline figure.
Cost drivers, roughly in order: the number of systems per workflow, how messy the data mapping is (German accounting fields, tax keys and customer numbers rarely line up across tools), the need for custom nodes, approval steps involving people, and any migration of historical records. Setting up and hardening a self-hosted instance is a separate line in the quote.
Running costs belong in the budget as well: a server or n8n Cloud plan, any paid n8n tier, and usage fees for connected services such as AI models. On self-hosted n8n these do not grow with each workflow step, which is often the main financial reason to move away from per-task pricing. If AI steps are involved, the AI automation guide explains how model costs are estimated.
What does an n8n automation agency maintenance retainer cover?
A maintenance retainer keeps the instance updated, watches failed runs, fixes broken connections and makes small changes. n8n ships updates frequently, and the APIs your workflows use change on their own schedules, so unattended instances drift into trouble.
Our care plans start from US$120/mo a month after two months of free maintenance. Typical monthly work includes applying n8n updates on a test copy first, then production; checking the error log and re-running failed items; renewing expiring credentials and tokens; adjusting a workflow when a connected tool changes its API; and a short monthly note on what ran, what failed and what changed.
What a retainer should not be is a lock-in. Your instance, workflows and credentials stay in your accounts, and the runbooks let your own IT or another n8n automation agency take over. The exact scope and notice terms are set out in your written quote; see our terms for the general conditions.
How to choose an n8n expert or n8n automation agency
Pick the provider that talks about failure, hosting and ownership before it talks about how many workflows it has built. Ask to see an error workflow and a runbook, not just a canvas screenshot.
- Will the instance and all credentials sit in accounts we own?
- How do you handle retries, duplicates and failed items?
- Where is execution data stored, and how long is it kept?
- Which of our tools need community nodes, and who maintains those?
- How are workflows version-controlled and documented?
- Who receives alerts, and what is the response process?
- Which n8n licence tier do we need, and why?
Good answers are specific: "PostgreSQL in your AWS account in Frankfurt, pruning after an agreed number of days, alerts to your Teams channel and to us". Vague answers about "enterprise-grade security" are a reason to keep looking. For a broader view of engaging developers abroad, see when a dedicated remote team makes sense.
Can an n8n automation agency add AI agents and model steps?
Yes. n8n includes nodes for calling language models and building agent-style workflows, and any model with an API can be reached through HTTP. That makes n8n a practical home for AI steps inside ordinary business processes.
The design rules are the same as for any AI automation: send the model only the fields it needs, prefer EU-hosted model endpoints, validate its output with rules before acting, and put a human approval step in front of anything irreversible. A classification step that routes emails is low-risk; an agent that can send offers or change orders on its own is not.
n8n's visual canvas also helps with the AI Act's AI literacy duty in a small way: staff can see exactly where the model sits in a process and what it decides. We add a short explanation to each AI workflow's runbook. When a workflow talks directly to customers, such as a chatbot, transparency rules apply; the GDPR compliant AI chatbot page covers that case.
How does an n8n automation agency move you off Zapier or Make safely?
The rule we follow as your n8n automation agency alternative: migrate one flow at a time, run old and new in parallel, and switch only when the outputs match. A big-bang migration of forty zaps on one weekend is how orders get lost.
We start with an inventory: every zap or scenario, what triggers it, which apps it touches, how often it runs and who depends on it. Many turn out to be unused and can be retired. The rest are grouped by system, because rebuilding all the lexoffice flows together is faster than jumping between tools.
During the parallel phase the n8n version runs in a "dry" mode that logs what it would do without writing to the target system, and we compare the logs with what the old flow actually did. Once a flow matches for an agreed period, we switch the trigger and disable the old one. Credentials are created fresh as service accounts rather than copied from personal logins, which is also a good moment to tidy up who has access to what.
Hiring an n8n automation agency in India from Germany: how it works
You talk to the developers building your workflows, in English, during your morning. India runs 3.5 hours ahead of German summer time and 4.5 hours ahead in winter, so a 10:00 call in Hamburg lands at 13:30 or 14:30 in India, and there is shared time every weekday.
Week one: a screen-share call where someone shows us the current manual process, access to a test account in each tool, and a one-page flow description we write and you correct. If we are self-hosting, we set up the instance in your cloud account in the same week. Week two: the first workflow runs against test data, you review it with us on a call, and we agree the switch-over plan.
Quotes are itemised in USD; invoices come from India in USD or EUR and are paid by Wise or bank wire according to the schedule in the approved quote. Nothing is billed before written approval. Your accountant handles the booking side.
What we do not do: visit your office, provide German-language phone support or act as your legal adviser on licences and data protection. If those are essential, a German n8n automation agency is the right call. For many teams, clear written documentation and fast WhatsApp replies matter more. More on the model is on offshore software development for Germany.
Worked example: a Shopware shop in Freiburg connects orders, invoices and DATEV
A hypothetical scenario, not a client story. Say a 12-person online shop in Freiburg sells outdoor gear on Shopware 6, invoices in lexoffice and sends its books to a tax adviser who works with DATEV. Today a staff member copies each paid order into lexoffice and exports a monthly file by hand.
The n8n design would have three workflows. Orders to invoices: a Shopware webhook fires when an order is paid; n8n checks it has not been processed before, maps customer and line items, and creates the invoice in lexoffice through its API, then writes the invoice number back to the order. Returns and withdrawals: when a return is registered, a credit note is prepared for approval in Teams rather than created automatically. Month-end export: approved documents are collected and passed on in the format the tax adviser agreed.
Hosting would be a small self-hosted instance in the shop's own EU cloud account with nightly database backups and execution data pruned after an agreed period. The error workflow posts to a Teams channel the owner reads. Build cost would start from the US$600 workflow price, with the three flows quoted together, and maintenance from US$120/mo after two free months.
What would be left to people: approving credit notes, answering the tax adviser's questions and deciding what happens with unusual orders. That split is deliberate.
n8n go-live checklist for German companies
Run through this before any workflow touches live data, whether you build in-house or with an n8n automation agency. Whichever n8n automation agency builds it, each line should have a name next to it.
- Instance in your company's account, in an EU location you chose
- Encryption key stored separately from database backups
- Execution data pruning set to a period your data protection officer agreed
- Service accounts with minimal permissions for every connected tool
- Error workflow sending alerts to a named person in your company
- Duplicate protection using source-system IDs
- Workflow JSON exports in your Git repository
- Runbook per workflow, including how to re-run failed items
- Restore test completed on a separate instance
- AVV list for every service in the data flow
Ten ticks and your automation will outlive any single developer, including us. Send the list with your questions and we will tell you which items your current setup already covers.