Lyron

n8n · Source-available · Self-hosting

n8n agency: plan, host and run your workflows.

n8n is an automation platform for workflows that go beyond simple trigger-action chains: with conditions, loops and custom code, over 400 integrations and the option to self-host. For companies that need more than linear processes, n8n is often the right choice – and Lyron, as a specialized n8n agency, handles build, hosting and operations.

  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

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 depending 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 handles even unusual system landscapes. Data can be enriched, transformed and validated between steps.

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

  3. Self-hosting & data sovereignty

    n8n can be operated on your own infrastructure – whether on-premises, 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 application has a ready-made connector. With the HTTP Request node, any REST API can be connected. For more complex cases, custom code (JavaScript) can also be executed directly in the workflow.

    Example: Connect internal industry software without a public integration to the workflow via its API.

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

    Incoming mail lands in the firm’s own folder

    Whether an email attachment, a scan of paper mail 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 recognizedSuccess
  • 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

Typical use cases with n8n

  • Lead intake & enrichment

    Capture leads from forms, enrich them with external data (company data, LinkedIn), create them in the CRM and assign them to the right sales rep automatically. Follow-up reminder after 48 hours.

  • Support ticket pipeline

    Turn form inquiries into tickets, post them in Slack and start an SLA timer. Escalate automatically on delays and send a customer feedback request once the ticket is closed.

  • Document generation

    Insert data from the CRM or a form into a document template, generate a PDF and send it for approval. Once approved, file it automatically and notify everyone involved.

  • Invoice & receipt processing

    Capture incoming invoices, extract the relevant data and transfer it to your accounting software. Generate a monthly summary report.

  • Monitoring & alerting

    Check external services or internal systems regularly. Send an alert via Slack, email or SMS as soon as problems occur – with an escalation chain if no one responds.

  • AI-powered classification

    Categorize and route emails or inquiries with an AI model. Important: the AI makes suggestions, the rules decide. It won’t replace clear logic, but it helps with unstructured data.

  • Data synchronization

    Keep contacts in sync between your CRM and newsletter tool, reconcile product data between shop and ERP and push changes in one system to the others automatically.

  • Content publishing

    Publish a blog post and share it on social media automatically – with an approval step before publication. Collect performance data later and report on it.

Best practices for stable n8n workflows

A workflow that works once is only the beginning. Production use needs structures that stay reliable when errors occur and requirements change.

  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 failure paths for permanent problems. Nothing should disappear without a trace.

  2. Logging & observability

    When something goes wrong, you need to be able to trace what happened. Structured logs, execution history and error notifications are not extras – they are mandatory for production workflows.

  3. Manage secrets securely

    API keys, passwords and tokens don’t belong in workflow code. n8n has built-in credential management – use it consistently. Regular rotation and minimal permissions reduce risk.

  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.

What does n8n cost? Licensing & hosting overview

n8n offers several options for different requirements. Exact costs depend on hosting, team size and the features you need. When you self-host on an EU server, the infrastructure alone often costs a low double-digit euro amount per month (as of July 2026).

Community Edition (source-available)

Free to self-host. Full functionality for individual users. No license fees – you only pay for your own infrastructure.

n8n Cloud

Managed hosting by n8n, billed by workflow executions. A quick start without your own infrastructure.

Enterprise

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

Lyron as your n8n agency: consulting, implementation and operations

We build n8n workflows that don’t just work but stay maintainable and traceable. Clean structure, documentation and error handling are part of every project – 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. A single workflow is usually live within 1–2 weeks; more complex processes spanning multiple systems typically take 2–4 weeks.

  1. Clean architecture

    Modular workflows, reusable components

  2. Documentation

    Every workflow clearly explained

  3. Handover or operations

    You take over – or we run it for you

Frequently asked questions about n8n

The scope of your n8n automation depends on workflows, systems and requirements. You receive a tailored quote before the project starts; support with monitoring and error handling is optional.
The Community Edition is source-available and free to self-host – you only pay for infrastructure, often a low double-digit euro amount 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-premises, 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 free consultation, we 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
  • Initial assessment of effort & benefit
Two people reviewing a result together on a laptop screen