Researching the biggest pain points with automation tools in the DACH region (Germany, Austria, Switzerland)

Questions
1

Hey everyone :waving_hand:

I’ve been using n8n for a while and love the flexibility — but I’ve also hit some walls, especially around debugging, error messages, and getting non-technical teammates onboard.

I’m currently researching how automation tools (n8n, Make, Zapier, Power Automate) are used in the DACH region (Germany, Austria, Switzerland) — and where the biggest pain points are. The goal: building a tool that’s designed for this market from day one (EU hosting, German UI, integrations with tools like DATEV, lexoffice, Personio).

Before writing any code, I want to hear from people who actually build workflows every day.

If you have 8 minutes, I’d really appreciate your input:
:backhand_index_pointing_right: Workflow-Automation im DACH-Raum — Interview

It’s anonymous, no signup, no sales pitch. Just honest questions about what works and what doesn’t.

Happy to share the results here once we have enough responses — could be interesting for the whole community to see where the common frustrations are across tools.

Thanks! :folded_hands:

4

Happy to share what I’ve seen across automation projects — these pain points come up constantly and are probably amplified in DACH given compliance requirements.

The biggest ones:

  1. Error visibility is terrible across all tools. When a workflow fails at 2am, Zapier sends a vague email, Make shows a confusing scenario log, n8n is better but still requires knowing which node to inspect. None give you “here’s what broke, here’s the data that caused it, here’s how to fix it” in plain language.

  2. Credential management at scale. Managing OAuth tokens for 20+ clients is a nightmare — tokens expire, re-auth breaks silently, no central view of what’s connected. n8n is slightly better with credential sharing but still fragile at volume.

  3. Non-technical handoff is basically impossible. You build a workflow, hand it to the ops team, one wrong click breaks everything. None of the tools have a good “end user mode” where someone can trigger a workflow and see results without touching the canvas.

  4. DATEV/lexoffice specifically — only handled via custom HTTP Request nodes hitting their APIs. No native integrations in any major tool. Personio has a basic Make integration but it’s mostly read-only.

  5. Pricing unpredictability on task-based models. Zapier at 50K tasks/month is ~$250. If a client’s workflow processes 10x the data unexpectedly, costs spike with zero warning. n8n self-hosted eliminates this entirely — big selling point for DACH businesses wanting predictable costs.

Would be curious to see the results when you publish them.

5

one thing flyclaw didn’t cover: data sovereignty anxiety is often the actual blocker, not the tooling. in practice, many DACH business owners wont green-light cloud automation for processes touching customer data even when it’s technically GDPR compliant — they need to explain their infrastructure to their own clients, and “EU region on AWS” doesnt always cut it. the gap between “legally compliant” and “what the client is comfortable with” comes up constantly in the german market, could be a useful question for your survey.