Lyron

n8n · Open source · Self-hosting

n8n agency: plan, host and run your workflows.

n8n is a powerful automation platform that sets itself apart from simple trigger-action tools. It offers real programming logic, hundreds of integrations, and the ability to self-host workflows. For companies that need more than linear processes, n8n is often the right choice – with Lyron as your specialised n8n agency for build, hosting and operations.

Discuss use case Compare all tools
  1. Self-hosting in the EU
  2. Over 400 integrations and your own APIs
  3. Error handling and monitoring
  4. Documented, no vendor lock-in
Server rack with cabling – a symbol for self-hosted n8n workflows in the EU
Use Cases

When n8n is the right choice

  1. Map complex logic

    n8n supports conditions, loops, branches, and data transformations directly in the workflow. This enables processes that respond to different scenarios – not just "if X, then Y", but "if X under condition A, then Y, else check B and C".

    Example: A lead is routed differently based on industry, company size, and source – with automatic data enrichment in between.

  2. Connect many systems

    With over 400 native integrations and the ability to connect any API, n8n connects even exotic system landscapes. Data can be enriched, transformed, and validated between steps.

    Example: Fetch data from legacy ERP via API, reconcile with CRM data, and write to BI tool.

  3. Self-hosting & data sovereignty

    n8n can be operated on your own infrastructure – whether on-premise, in your own cloud, or with a European provider. Sensitive data never leaves your control, which can be crucial for regulated industries or strict data protection requirements.

    Example: Process health data automatically without transferring it to US cloud services.

  4. Custom API connections

    Not every software has a ready-made connector. With the HTTP node, any REST API can be connected. For more complex cases, custom code (JavaScript) can also be executed directly in the workflow.

    Example: Integrate internal industry software without public API into the workflow.

Workflow

How a workflow runs in n8n

Using a law firm's digital mail intake as the example: five steps from the scanned letter to the confirmed deadline. The execution log shows, with sample data, what n8n records on every run.

  1. Step 01 · Trigger

    An item lands in the firm's own store

    Whether an email attachment, a scan of paper post or a PDF exported from the beA: the workflow starts as soon as a document sits in the firm's intake folder. The beA itself stays in the firm's hands.

  2. Step 02 · OCR & AI

    Read and classify

    A local OCR component makes the document searchable, and a locally running language model picks out case numbers, opposing parties and courts. The document never leaves the firm's own server.

  3. Step 03 · REST interface

    Assign and file

    Through the practice-management software's interface, n8n files the item in the matching case and sends the responsible lawyer a short summary. Uncertain cases aren't guessed at – they go to a queue for manual assignment.

  4. Step 04 · Approval

    Deadlines only with human confirmation

    If the workflow detects a possible deadline trigger, it creates an approval task with a proposed date. The deadline is only entered once the lawyer confirms it; if no one responds, a timeout escalates the task to the partner.

  5. Step 05 · Log

    Traceable in the execution history

    Every execution is logged with its steps, and every deadline confirmation is documented. If a step fails, retry logic and notifications kick in – nothing disappears without a trace.

n8n · Execution log Sample data
n8nExecutions
  1. Intake
  2. Classify
  3. Case file
  4. Approval
  5. Log

Workflow: law firm mail intake

Instance
self-hosted · server in Germany

Latest execution

  • 08:14Scan in the intake folderStart
  • 08:14OCR · case number recognisedSuccess
  • 08:15Filed to case · lawyer notifiedSuccess
  • 08:15Second item without a matchManual
  • 08:15Deadline trigger · approval taskWaiting
  • 09:02Deadline confirmed · calendarSuccess
Mail intake per day~40 min instead of ~2 hrs
ApprovalThe workflow only enters a deadline after the lawyer has confirmed it.

Workflow and time values from our law firm case study

Practice

Typical use cases with n8n

  • Lead Intake & Enrichment

    Capture lead from form, enrich with external data sources (company data, LinkedIn), create in CRM, and automatically assign to appropriate sales rep. Follow-up reminder after 48 hours.

  • Support Ticket Pipeline

    Create form inquiry as ticket, post in Teams or Slack, start SLA timer. Automatic escalation on delay. Send customer feedback request after completion.

  • Document Generation

    Insert data from CRM or form into document template, generate PDF, send for approval. After approval, automatically file and notify parties.

  • Invoice & Document Processing

    Capture incoming invoices, extract relevant data, transfer to accounting software. Generate monthly summary as report.

  • Monitoring & Alerting

    Regularly check external services or internal systems. Immediately alert via Slack, email, or SMS when problems occur. Escalation chain if no response.

  • AI-Powered Classification

    Categorize and route emails or inquiries via AI model. Important: AI provides suggestions, logic decides. Don't expect miracles, but useful support for unstructured data.

  • Data Synchronization

    Keep contacts synchronized between CRM and newsletter tool. Reconcile product data between shop and ERP. Automatically transfer changes in one system to others.

  • Content Publishing

    Publish blog post, automatically share on social media channels. With approval step before publication. Later collect performance data and report.

Client cases

n8n in practice

Three anonymised projects in which n8n is at the core of the automation – from a law firm to a trades business.

Quality

Best practices for stable n8n workflows

A workflow that works once is just the beginning. For production use, structures are needed that remain reliable even with errors and changes.

  1. Error Handling & Retries

    Every external call can fail – network problems, API limits, temporary outages. Good workflows have retry logic for transient errors and defined fail paths for permanent problems. Nothing should disappear without a trace.

  2. Logging & Observability

    When something goes wrong, it must be traceable what happened. Structured logs, execution history, and notifications for errors are not extras, but mandatory for production workflows.

  3. Securely manage secrets

    API keys, passwords, and tokens don't belong in workflow code. n8n offers credentials management – use it consistently. Regular rotation and minimal permissions reduce risks.

  4. Versioning & Change Management

    Workflows evolve. With Git integration or regular exports, changes can be tracked and rolled back if problems occur. Document why something was changed.

Costs

What does n8n cost? Licensing & hosting overview

n8n offers various options for different requirements. Exact costs depend on factors like hosting, team size, and required features. For self-hosting on an EU server, pure infrastructure costs often stay in the low double digits per month (as of July 2026).

Community Edition (Open Source)

Free to self-host. Full functionality for individual users. No license fees, but own infrastructure costs.

n8n Cloud

Managed hosting by n8n. Entry possible, scaling by workflow executions. Quick start without own infrastructure.

Enterprise

Additional features like SSO, extended permissions, and support. For teams and organizations with higher requirements.

Collaboration

Lyron as your n8n agency: consulting, implementation and operations

We implement n8n workflows that not only work, but are also maintainable and traceable. Clean structures, documentation, and error handling are standard with us – not extras you have to book separately.

An n8n project with us runs in four steps: process mapping, a prototype with real data, hardening with error handling and monitoring, then handover or ongoing operations. Simple workflows often go live within days; more complex processes spanning multiple systems typically take 2–4 weeks.

  1. Clean Architecture

    Modular workflows, reusable components

  2. Documentation

    Every workflow explained understandably

  3. Handover or Operation

    You take over – or we operate

FAQ

Frequently asked questions about n8n

We build individual n8n workflows from €490; larger automation projects range from €890 to €5,900. Ongoing support with monitoring and error handling starts at €290 per month – entry prices and the process are on our pricing page.
The Community Edition is open source and free to self-host – you only pay for infrastructure, often in the low double digits per month on an EU server (as of July 2026). n8n Cloud is billed by workflow executions, and the Enterprise edition adds SSO, extended permissions and support.
It depends on your data protection requirements, internal resources and desired level of support. n8n Cloud gets you started quickly without your own infrastructure; self-hosting on a European server or in your own environment gives you full control over sensitive data. We advise you on the right option and can handle setup and operations.
Yes. Because n8n can be self-hosted – on-premise, in your own cloud or with a European provider – sensitive data never leaves your control. That makes n8n particularly attractive for regulated industries and companies with strict data protection requirements.
n8n pays off when you need complex logic with conditions, loops and branching, want to connect your own APIs, or need to host workflows yourself. For simple, linear standard automations, Make.com or Zapier are often quicker to set up – we recommend the tool that fits your use case.

Free consultation · 30 minutes

Your n8n workflow, built properly.

Tell us about your process. In the intro call we will tell you whether n8n fits, whether self-hosting or n8n Cloud makes more sense and what the path to your first workflow looks like.

  • Free & no obligation
  • 30 minutes via Google Meet
  • First view of effort & benefit
Discuss use case Pricing & process
Two people reviewing a result together on a laptop screen