Zaps and scenarios fail quietly.
A login expires or a field changes, and the workflow stops. Nobody finds out until a customer asks what happened.
n8n, Make & Zapier automationWorkflows built, fixed,
or moved to the right platform.
I build, fix and move automations in n8n, Make and Zapier. I connect your apps through their integrations and APIs, and handle the errors that cause silent failures, so a broken step gets noticed instead of quietly losing data.
Free 30-minute Automation Growth Audit. Bring one task. No prep needed.
The usual headachesAutomations are easy to start
Automations are easy to start
and hard to keep running.
Nobody knows how it all fits together.
Dozens of automations built by different people, and no map of what triggers what.
Costs creep up.
Task counts grow with the business, and some workflows use far more steps than they need.
Data is still copied by hand.
Some apps have no ready-made connector, so the last step is still a person with two browser tabs.
For teams that rely on automation, or want to.
Businesses running anything from a handful to a few hundred automations, teams that have outgrown do-it-yourself workflows, and owners who want a new integration built properly the first time.
Not a fit: if you need a full custom app rather than connected workflows, I’ll say so on the call and suggest what to look for instead.
- You use Zapier, Make, or n8n, or plan to
- Some workflows break, duplicate, or nobody fully understands them
- You need an app connected that has no simple built-in integration
- You want alerts when something breaks, not just a working demo
What I build
Example workflows.
Most projects are one of these, or a mix.
New workflows and API integrations
Multi-step workflows between your apps, including custom API calls and webhooks where there’s no ready-made connector.
n8n, Make, Zapier, REST APIs, webhooks
Automation repair
I find out why a Zap, scenario or n8n workflow breaks, stalls or creates duplicates, fix the cause, and add error handling so it fails loudly next time.
Run history, logs, integration settings
Automation audit and cleanup
A list of what you have, what each workflow does, what it costs to run, and which ones overlap, are fragile or can be switched off.
Your Zapier, Make, or n8n account
Zapier to n8n or Make migration
Rebuild workflows on a platform that suits your volume, run old and new side by side, then switch over when the results match.
Zapier, Make, n8n Cloud or self-hosted
Monitoring and alerts
Error workflows, retry rules and alerts to email or team chat, so a failure gets noticed quickly and has a clear owner.
Error handlers, email, team chat
AI steps inside workflows
Sorting, summarizing and pulling out data with AI models, with checks and a human review step for uncertain results.
OpenAI or Claude inside n8n, Make or Zapier
See finished workflow logic.
My Work page has three working tools I built: lead routing, document checks and a time-value planner. They show the kind of rules, checks and structured output I build into real workflows.
Which platform should I use?Zapier, Make, or n8n?
Zapier, Make, or n8n?
It depends on the workflow.
| Criteria | Zapier | Make | n8n |
|---|---|---|---|
| Best for | Straightforward workflows across a very large app library; the easiest start for non-technical teams | Visual, multi-branch scenarios with detailed data handling | Complex logic, custom code, higher volumes, and teams that want the option to self-host |
| How usage is counted | By tasks: each successful action step counts | Usage-based: each module run counts toward your plan | By workflow executions on n8n Cloud; self-hosting is also possible |
| Hosting | Cloud | Cloud | Cloud or self-hosted |
| Learning curve | Lowest | Moderate | Highest; suits teams comfortable with technical detail |
| Watch out for | Cost at high task volumes; complex logic gets awkward | Large scenarios become hard to read without documentation | Self-hosting means someone owns updates, backups, and security |
Features and pricing change often, so I check current plans for your case during scoping. I use all three and recommend one per workflow, not one for everything.
When migrating from Zapier makes sense, and when it doesn’t
Moving to n8n or Make can lower running costs or simplify awkward logic, especially at higher volumes. It isn’t free: workflows have to be rebuilt and retested, and someone on your team has to learn a new tool. If your Zaps are few, simple and reliable, the honest answer may be to leave them alone and fix the one that breaks. I’ll show you the trade-off for your actual workflows before recommending a move.
How it worksFrom first call
How I workFrom first call
to launch.
- 01
Free audit
We look at the workflow or account, what breaks, and what it should do.
- 02
Scope & plan
We agree the build, the repair list or the migration order, and how we’ll check it works.
- 03
Build & test
I build with error handling, test with realistic data, and run old and new side by side where needed.
- 04
Launch
I switch it on, check the results, and explain how each workflow runs.
ToolsThree platforms.
Three platforms.
One recommendation per workflow.
Most projects also touch the apps your team already lives in. If an app has an API or can send webhooks, I can usually connect it.
What you get.
- Workflows with error handling and alerts, not just the happy path
- A plain-English explanation of what each workflow does and what triggers it
- Test results for normal cases and exceptions
- Admin access and credentials kept in accounts your business controls, where possible
Wherever I can, I build in accounts your business owns, so the workflows, logins and data stay yours.
Can you fix a Zap or scenario someone else built?
Yes. I read the run history and settings, work out what it was meant to do, fix the cause, and add an alert so the next failure doesn’t go unnoticed.
Do you work with self-hosted n8n?
Yes, and n8n Cloud too. Self-hosting gives you more control but needs someone responsible for updates, backups and security, so we agree who that is before choosing it.
Will a migration interrupt our business?
It shouldn’t. I rebuild workflows next to the old ones, compare the results, and switch over one workflow at a time once they match.
What if an app has no integration?
If it has an API or can send webhooks, I can usually connect it. If it has neither, I look at options like email parsing or scheduled exports, and tell you if none of them would be reliable.
Related services
All servicesOften built together.
CRM automation
CRM and ClickUp workflows that keep records clean and turn every handoff into a task.
Explore this service: CRM automationDocument processing automation
PDFs, invoices, and forms turned into checked records, with uncertain fields sent for review.
Explore this service: Document processing automationLead follow-up automation
Reply to new inquiries fast, assign an owner, and follow up until there’s a next step.
Explore this service: Lead follow-up automationFree 30-minute call
Show me one task.
Show me one task.
I’ll tell you what I’d automate.
- Free
- 30 minutes
- You talk to me
Book a free 30-minute call
Bring the job that eats the most time.