◆ Service
Workflow & Business Process Automation
Automation that a business can actually run on.
I design and build workflow automation with n8n — connecting the applications, APIs and services a business already uses so work happens without someone copying data between tools by hand. I've also written a book on exactly this.
01 — The Problem
Most businesses already have an informal version of automation: someone copying data from one tool into another, a spreadsheet nobody fully trusts, a process that only works because one person remembers every step.
02 — The Solution
I turn that into an explicit, reliable workflow: idempotent, with a real failure path and a log of what happened. That's the difference between a workflow that runs once in a demo and one a business depends on every day.
03 — What's Included
- Workflow design across the tools you already use
- API and webhook integrations between systems
- Error handling and retry logic, not just the happy path
- A log a human can read when something needs checking
- Documentation so the workflow isn't a black box
- Handover or ongoing support, as needed
04 — Process
- 01
Map the manual process
What actually happens today, tool by tool, step by step.
- 02
Decide what's a workflow vs. an application
Automation is the right tool for "when this happens, do these steps." A real data model and interface needs are a different job.
- 03
Build with idempotency in mind
So a workflow that runs twice doesn't create duplicate orders, emails, or records.
- 04
Add failure handling
Retries with backoff, and a clear path to a human when a step still fails.
- 05
Hand over or maintain
Documented, and either handed off or supported ongoing.
05 — Technologies
- n8n
- REST APIs
- API integrations
- Webhooks
06 — Related Reading
07 — FAQ
- What's the difference between this and just using Zapier myself?
- Off-the-shelf automation tools are fine for simple, single-step connections. Once you need error handling, conditional logic, your own data model, or something that runs unattended and has to be right, that's where custom-built n8n workflows earn their cost.
- Can you connect tools that don't have an official integration?
- Usually yes, as long as the tool exposes an API or webhook. I'll tell you upfront if something genuinely isn't possible rather than promise and fail to deliver.
- Do you only build with n8n?
- n8n is where most of this work happens, including the workflows behind my own projects and my book on the subject. For a given job, the right tool is whichever one fits — I'll say so if n8n isn't it.
Have a project that needs this?
Tell me what you're trying to build and I'll tell you honestly whether — and how — it fits.