Agentic process automation.
I build business process automation on n8n — with AI agents where a judgement call is needed, and plain logic where a rule is enough. Where low-code runs out, I write the microservices that take over.
Process automation in most companies stops at the same place: the simple flows work, and the genuinely expensive ones need a judgement, an exception, or a document no form will ever capture. That boundary is where my work starts.
I am the creator of n8n-mcp — the tool that lets AI agents build working n8n automations instead of guessing. It has over 128,000 users, including teams at Deutsche Telekom, PayPal and Mercado Libre. It is the same approach I bring to client work.
What I automate
Quoting and inbound requests
From an enquiry in the inbox to a finished quote: reading the requirements, matching them to your pricing and catalogue, generating the document and handing it to a salesperson to approve.
Invoicing and back-office processes
Many suppliers, many inboxes, many formats — reduced to one register ready for accounting, with duplicate and exception handling built in.
System-to-system integration (iPaaS)
CRM, ERP, e-commerce, spreadsheets, supplier APIs. I connect systems that were never designed to talk to each other, and keep those connections working when the other side changes.
Operational agents
Where a process needs judgement — qualifying a lead, classifying a ticket, choosing a path — I place an agent with a clearly bounded scope and an explicit point where it hands the case to a human.
Microservices where low-code ends
Custom APIs, scrapers, document converters and compute services — written when no ready-made block exists, or when one would become the bottleneck.
Training your automation team
I teach your team to build their own n8n automations and stay on regular office hours to review their work and unblock the harder cases.
Who this is for
- Companies where several people spend a measurable part of the week retyping data between systems.
- Teams already running n8n or another iPaaS tool who have hit its ceiling.
- Organisations whose automation has to handle documents, not just structured data.
- Companies that want their own team building, rather than staying dependent on a vendor.
How I run it
- 01Mapping the process
I sit down with the people who do the work today and write it out step by step — including the exceptions nobody remembers until one occurs.
- 02First flow in production
I start with one well-chosen process and finish it. A working flow in production is a better argument than a plan covering ten.
- 03Extending
Further processes go onto the same infrastructure, with the same monitoring, error handling and deployment path.
- 04Handover
The team gets documentation, access and training. The goal is a company that extends its own automations.
Implementations
From single flows to systems where the client's own team now maintains more than two hundred automations.
Over 200 workflows on one platform — marketplace automation across 6 countries, agentic product research, custom microservices and an internal automation team trained to work independently.
Read the case studyFor a CFO-as-a-Service firm: an agentic content engine publishing one article a day, and a Coda-based finance operating system — a counterparty registry, an income-and-expense ledger fed straight from invoices, and a hub that shows who needs paying and how much.
Read the case studyCost invoices arriving across seven team inboxes are found, read, de-duplicated and filed automatically — into a Google Drive archive and a Google Sheets register that's ready to hand to the accountant. Twelve connected n8n automations.
Read the case studyAI reads broker offerings from emails and flyers (vision), fuzzy-matches them against a property database, enriches them with neighbourhood data and generates Letters of Intent in one click.
Read the case studyFrom a file in a folder to a live ad — AI analysis of images and videos, French copy in three positioned variants, standardised naming and automated upload to Meta Ads.
Read the case studyCommon questions
- Why n8n rather than Make or Zapier?
- n8n can be self-hosted, so data never leaves your infrastructure, and there is no per-operation limit to wreck the economics at volume. It also lets you drop into real code where the ready-made blocks stop. If Make is genuinely enough for someone, I say so.
- Does automation have to involve AI?
- No, and often it shouldn't. A model is needed where something has to be understood or judged. Where a rule suffices, the rule is cheaper, faster and predictable.
- What happens when an automation breaks?
- Every flow has error handling and alerting — a failure is loud, not silent. Business-critical processes also keep a manual path so a breakage doesn't stop the work.
- Can our team handle this without you?
- That is the point. The training and office hours exist so the company doesn't end up dependent on me. At several clients the team now builds most of the automations themselves.