From the PMC teamDevelopment projects start in 2027. Plan yours now to secure an early start.

Workflow automation

Let your processes run themselves, with n8n.

We design, build and run n8n workflows that move data between your systems, ask the right person at the right moment and leave nothing to copy by hand. On servers we run for you, or in your own infrastructure.

  • Fast to deliver
  • Built to last
  • Secure from day one
11+years of building software for finance, IT and project teamsAbout the team
Workflow automation

Our workflow automation services

We find the hand-offs that cost your team hours, automate them in n8n and keep them running, with a person approving what matters.

Process analysis and workflow design

The process mapped with your team and turned into triggers, steps and error handling.

Discuss this service

What we cover: Self-hosted n8n on your servers or ours, on the Community or Enterprise licence, whichever fits. Any system with an API, a database or a file export can be part of a workflow.

The team behind PMC, trusted by
  • BNP Paribas
  • Allianz
  • Hexagon
  • Hewlett Packard Enterprise
  • Enapter
Solutions

Workflows we automate

  • Invoice intake

    Invoices arrive by e-mail, are read, checked against the order and sent for approval.

  • Employee onboarding

    One entry in HR creates accounts, licences, equipment orders and the welcome e-mail.

  • Lead routing

    New enquiries are enriched, scored and handed to the right salesperson in the CRM.

  • Morning report

    Figures from several systems are collected every morning and sent as one report.

Your team still copies data from one tool to the next?

Name the task. We show you the workflow that does it, which tools it connects and where a person still says yes.

Plan your first workflow
A worked example

How a project like this runs.

Example

Invoice intake from inbox to booking

The situation

Invoices arrive in a shared mailbox as PDFs. Someone opens each one, types the data into accounting and forwards larger amounts for approval.

What we do
  1. The workflow starts on every new e-mail with an invoice attached.

  2. An AI step reads supplier, amount and order number; the order is looked up in the ERP.

  3. Above an agreed amount the approver is asked in Microsoft Teams; below it the invoice is prepared for booking.

  4. The invoice is booked in DATEV, and anything unclear goes to a named person with the reason.

The result

Invoices are captured the day they arrive, and the team handles only the exceptions.

An illustrative example of the way we work, not a named customer.

AI inside

AI steps inside your workflows

Each one with a person's approval where it matters.

  • Document classification
  • Data extraction
  • E-mail and ticket triage
  • Summaries for approval
  • Anomaly alerts
  • Human approval steps
  • Routing by content
  • Scheduled AI reports
  • Calls to your systems through MCP
Why it pays

Why automate your workflows

01

Hand-offs that run on their own

Today
Data copied by hand from e-mails and exports into the next system.
With it in place
Each hand-off runs on its own, started by the event that triggers it.
Built to run

Automations you can trust with real work.

What keeps a workflow running when the systems around it change.

Errors handled, not hidden
Failed steps are retried, and anything that still fails lands with a named person, not in a log nobody reads.
Approval where money moves
Payments, bookings and messages to customers wait for a person to approve them.
Every run traceable
Each run is logged with its input, its steps and its result.
Versioned and documented
Workflows are kept in version control and described, so your team can follow and change them.
What you receive

Everything you need to own the result.

  • The workflows, versioned in your repository
  • n8n installed and secured on your servers or ours
  • Custom nodes for systems without a ready-made connector
  • Error alerts that reach a named person
  • A short description of every workflow: trigger, steps and owner
  • Backups, monitoring and updates, if we host it

Is it right for you?

A good fit when
  • A process that repeats daily or weekly between two or more tools
  • Clear rules for who approves what
  • Systems with an API, a database or a file export
Not the right fit when
  • A process that needs a new judgement at every step
  • A one-off data migration, which is better done as a script
Speed, quality and security

Fast does not have to mean fragile.

Every project is held to the same standard, whatever the service. It is the standard we build and run PMC to every day.

  • Fast to deliver

    Results in weeks, not quarters.

    • A working version at the end of every short cycle
    • Releases through an automated pipeline, not by hand
    • Small changes shipped often, so value arrives early
  • Built to last

    Software your team can still understand and change years from now.

    • Every change built and tested automatically before it is merged
    • Unit, API and end-to-end tests in a real browser
    • Documentation and a clean handover, or we run it for you
  • Secure from day one

    Security is part of the build, not a check at the end.

    • OWASP Top 10 and BSI IT-Grundschutz as the reference
    • Dependencies and images scanned for known vulnerabilities in every build
    • Access by role, changes logged, secrets kept out of the code
How we work

From a manual process to a workflow that runs itself.

  1. Map the process

    With your team we write down the triggers, steps, exceptions and who approves what.

  2. Build the workflow

    In n8n, with connectors to your systems and custom nodes where none exist.

  3. Test with real cases

    The workflow runs on real examples, including the ones that should fail, before it goes live.

  4. Host and look after it

    On your servers or ours, with backups, monitoring and updates.

Automations nobody dares to touch any more?

We document, test and rebuild them in n8n, versioned and monitored, so your team can change them again.

Review your automations
Ways to work with us

Choose how much of the work you hand over.

From one clearly scoped project to a team inside your business and the long-term running of what we built. Every model has one accountable partner: Virtual Eye.

  • For a defined result

    Fixed-scope project

    You know what you get before the build starts: a concept, a prototype and a fixed scope come first.

    • A workshop on your process and the result you need
    • Concept, prototype and fixed scope before production code
    • A working version at the end of every short cycle
  • When the problem is not yet clear

    Forward deployed team

    A small Virtual Eye team works inside your business, learns how work and money really move, and delivers the solution with your people.

    • One lead for management, plus the engineers who build
    • Outcome and scope agreed in writing
    • A demo every week
  • For software you already run

    Takeover and modernisation

    We take over an existing application, make it safe to change, then develop it further step by step.

    • What exists is documented and tested first
    • Stabilised before anything new is added
    • Further development in small, tested releases
  • After go-live

    Run and evolve

    We host, monitor, update and support your applications on our servers, in your cloud or on-premises.

    • Monitoring and alerts that go straight to our team
    • Backups, updates and security patches
    • Support and further development from the team that built it
Customers

What customers say about working with us.

Quotes about the Virtual Eye team from PMC projects: the same people who would work on yours.

“Well thought-out concepts, tailored precisely to us. Very competent and always friendly, even during the stressful implementation phase.”
Iris HummelManager Infrastructure Services Sales DACH, Hewlett Packard EnterpriseTranslated from German
“PMC provides valuable support in day-to-day business and the team is very reliable, serious and friendly!”
Hao LiCentral Project Office PMO, Allianz Global Corporate & Specialty SE
“As a customer from day one, we have found reliable, fitting solutions with Virtual Eye throughout the years. Above all, the fast and flexible service.”
Sebastian StepferExecutive Director Public Safety EMEA Region, HexagonTranslated from German
Tech stack

The tools we use for this.

We choose them for your systems and your team, and we document every choice.

Enterprise platforms we extend, integrate and automate, so they work with the rest of your systems.

Microsoft business platforms

  • Microsoft Power Platform
  • SharePoint
  • Dynamics 365
  • Power BI
  • Dataverse
  • Microsoft Teams
  • Microsoft Graph
  • Microsoft 365
  • Azure OpenAI

ERP and finance

  • SAP
  • Microsoft Dynamics 365
  • Oracle
  • Odoo
  • DATEV

CRM and customer platforms

  • Salesforce
  • HubSpot
  • Zoho
  • Bitrix24
  • Dynamics 365 CRM

RPA and workflow automation

  • UiPath
  • Blue Prism
  • EasyRPA
  • Power Automate
  • WorkFusion
  • n8n
  • Make
  • Zapier

Low-code and rapid development

  • Mendix
  • Power Apps
  • Power Pages
  • FlutterFlow
  • Supabase

Service management

  • ServiceNow ITSM
  • ServiceNow ITOM
  • ServiceNow CSM
  • ServiceNow HRSD
  • ServiceNow Security Operations

E-commerce, CMS and PIM

  • Shopify
  • BigCommerce
  • Adobe Commerce (Magento)
  • WooCommerce
  • Shopware
  • Spryker
  • Sylius
  • PrestaShop
  • OpenCart
  • WordPress
  • Drupal
  • Joomla
  • Akeneo
  • Pimcore
  • Stripe

Collaboration

  • Jira
  • Confluence
  • Notion
  • Slack
Your technology is not listed?

Tell us what you run. If we have not worked with it yet, we say so, and tell you how we would approach it.

Talk to our engineersSee all technologies
Industries we serve

Workflows for the industries we know

Years of PMC have taught us how these industries approve, buy, report and get audited.

Banks

Approval chains with a full audit trail, from request to booking.

  • Invoice approval workflows
  • Access and change requests
  • Four-eyes approvals enforced
Questions

Questions teams ask before they start.

Why n8n?

n8n can run on your own servers, connects to hundreds of applications and lets us add our own code where a standard step is not enough. If you already use Make or Zapier, we work with those too.

What happens when a workflow fails?

Failed runs are retried, reported and listed in one overview with the data they were working on, so nothing is lost without anyone noticing.

Can our own team change the workflows later?

Yes. n8n shows every workflow as a diagram. We document each one and train the people who will look after it.

Which systems can a workflow connect?

Any system with an API, a database or a file export. Where no ready-made connector exists, we write a custom node for it.

Can AI be part of a workflow?

Yes. Language models read documents, sort requests and draft answers inside the workflow, and a person approves where it matters.

Tell us what you want to build.

Describe the process, the systems involved and when it should go live. We reply with a first assessment and the next step.

Or write to us directly: hello@virtual-eye.com

What happens next?

  1. You write to us

    What you want to build, the systems involved and when it should go live.

  2. A first assessment

    We reply with a first assessment and the next step.

  3. A workshop

    On your process and the result you need, before any technology is chosen.

  4. A fixed scope

    A concept, a prototype and a fixed scope before the first line of production code.