What we actually deliver
Most requests start with a bottleneck, not a product name. Enquiries sit in inboxes. Support is late. Someone types the same record into three tools. That is the work. Which tools we have connected is on the tools page.
-
n8n
n8n is open-source software that links your systems: triggers, approvals, failure paths. The flows stay readable. enaudo is an n8n affiliate, disclosed on the n8n page.
-
Windmill
Windmill is code-first: the flow lives as a program, not only as a chain of click-together blocks. We use it when logic, tests and versioning matter.
-
Small apps
If the process needs a surface, we build a slim app: a form, an internal view, an approval. Only when it carries the flow.
-
Custom microservices
Microservices are small extra programs for checks, domain logic or internal APIs. The flow calls them; the code carries the load.
-
Open-source integration
Proven open-source software becomes part of the flow: operated, connected, documented.
-
Managed hosting
Managed hosting means we run the server, updates and whatever keeps the process going. You use the flow without nursing the stack.
Examples, not packages
These are patterns. The first order comes from your bottleneck. What we build and how you will judge success is written down before we start.
-
Onboarding
Offer accepted, checklist, access prepared, welcome mail as a draft. Send and activation after approval.
-
Offboarding
Handover, proposal to remove access and licences, removal after approval, device return.
-
Several channels, one case
Mail, chat, forms and internal tools become one case. Status, ownership and the next step sit in one place.
-
Customer support with assignment
Ticket from mail or chat. AI proposes team, person and urgency, a person confirms. Draft reply, send after approval.
-
Documents into accounting
Invoices and receipts from the inbox or chat are recognised, checked and filed in the accounting tool. Duplicates stay out.
-
Appointments and capacity
Calendars and line-of-business systems say what is still free. Enquiries get an honest answer without matching lists by hand. Deadlines for contracts and certificates come back as reminders.
-
CRM from day-to-day work
Hints from chat, files and mail become contacts and cards. What already exists is not created twice.
-
AI with approval
Models may draft and classify. They send, book or commit only when a person agrees.
-
Tools and interfaces
Salesforce, mail, Lexware, chat and cloud: what we have connected and how almost any tool fits.
Operations: usually managed hosting
For most teams, managed hosting is the easier path. We take the instance, updates and the parts without which the process stops. New features and rebuilds remain separate work, kept apart from day-to-day operations.
Self-hosting stays available if you want to keep the infrastructure. The instance then runs on your environment or an EU environment we propose. You carry ongoing server cost. Workflows and code stay in your hands. The contract draws that line.
Privacy in the project, not only on the website
The privacy policy covers enaudo.de. In projects we settle separately: which data moves, where the instance lives, who has access, and what is deleted or handed over after the order. Credentials live in the instance, not in chats.
Operations and backups run on European infrastructure. That does not replace a processing agreement. For AI we use systems in the EU, including capable open-source models. US models only if they are hosted in the EU. AI is optional and tied to approval when something goes outside. There is no hidden training on your customer data. We follow the GDPR.
- Clarify which systems and fields are actually needed
- Instance in the EU, access by person, revocation after the project
- AI in the EU: open-source models, or other models only with EU hosting
- Providers and purposes for this website are in the privacy policy
From bottleneck to a running automation
You can read the path from the first conversation to maintenance on the process page. Automation nobody can explain after three weeks is more expensive than the routine it replaced.
- Capture the as-is flow, systems and real sample data in conversation
- Prioritise by value and risk, not the loudest idea
- Write the brief and acceptance criteria before building
- Implement with n8n, Windmill, microservices and open source where they fit
- Handover or managed hosting, both documented
What is out of scope
We do not promise a blanket time saving in two weeks. Shop-floor RPA and off-the-shelf packages without a discovery conversation are out of scope. If a process is not worth automating, we say so before there is an order.
Frequently asked questions
Who are the services for?
SMEs, service businesses and teams in Berlin and across Europe who need operational automation. Not enterprises tendering a large integration programme.
Do you only work with n8n?
n8n connects flows because it can be extended and inspected. When code is the better form, Windmill comes in. Microservices, small apps and open-source software are routine once stock building blocks are not enough.