n8n automation that holds up in production

Why n8n, and why not only n8n

n8n can run in the EU and can be extended with JavaScript. For companies with data-protection constraints that is often the difference versus services that only live in the US.

Still, n8n is the connecting layer, not the whole architecture. Windmill takes flows that are clearer as code. Microservices carry domain logic and load. Small apps give the process a surface when it needs one.

• Managed hosting as the usual operations model. Self-hosting if you want to keep the infrastructure
• Windmill when the flow is clearer, testable and versioned as code
• Custom services, small apps and nodes when stock integrations are not enough
• Human approval before send, where mail or bookings cannot be undone
• Handover of workflows and operating notes, even if we keep running the stack

When the flow needs code

n8n is strong when systems are linked, approvals are set and failure paths stay visible. Once the logic has to be longer, testable and followable in Git, we write it as code. For that we use Windmill: scripts instead of a long chain of click-together blocks.

Small apps come in when people have to operate the flow: a form, an internal view, an approval. The server sits in the same operations as the automation, in the EU.

What matters in practice

A flow that is green in a demo often fails on empty fields, API limits, time zones, duplicate events, or a message that should never have left the building. Failure paths, clean retries and approvals are part of delivery.

• autorenew

  Errors and retries

  Explicit error branches, inspectable logs and defined retries. The flow should not simply stop mid-customer process.

• key

  Access and secrets

  Credentials live in the instance, not in chat threads. Who may access what is in the statement of work, including revocation after the project.

• hub

  Tools and interfaces

  Salesforce, mail, Lexware, chat and cloud: what we have connected and how almost any tool fits.

• psychology

  AI as a layer

  Models may prepare text and classification. Binding steps stay rule-based or require approval.

Managed hosting first, self-hosting as an option

Managed hosting means we operate, update and monitor. For most clients that is the easier path, because the instance, updates and system-critical work do not sit in their team. New features and larger rebuilds remain separate work.

Self-hosting means the instance runs on your infrastructure or an EU environment we propose. You carry ongoing server and model cost and keep the workflows. The contract draws that line. Operational data stays on European infrastructure. Providers are named in the privacy policy.

Note: enaudo is an n8n affiliate

enaudo is an n8n affiliate. If you start n8n Cloud through one of our links, n8n may pay us a commission. The price stays the same for you. Our recommendation follows your process, not the commission. If n8n is not the right fit, we say so before there is an order.