(01) n8n automation
n8n workflows that keep running.And a Zapier bill that stops growing.
I build n8n workflows, self-hosted or on n8n Cloud, and move Zapier and Make setups across without losing a run. Lead routing, CRM and Stripe webhooks, invoice syncs and weekly reports, each with retries, an alert when something fails and a note of what it does.
Free 30-minute call · No commitment · Reply within a day
- Self-hosted or Cloud
- Zapier and Make moves
- Alerts on failed runs
- Quoted to your needs
(02) When to call
Signs your automationsneed a developer.
The Zapier bill keeps climbing
Per-task pricing was cheap at the start. Now a flow that runs every few minutes costs more each month than hosting n8n yourself.
Runs fail quietly
A webhook times out or an API changes, and nobody hears about it until a customer asks where their order went.
Only one person can change it
Forty steps, filters inside paths and no notes. Everyone else is afraid to touch it.
Your data has to stay with you
Customer or health data you'd rather not send through another company's servers, so you want n8n on your own.
(03) Where to start
Workflows teamsask for most.
Leads into your CRM
Web forms, ad leads and booking tools go into HubSpot, Pipedrive or Airtable, are de-duplicated and routed to the right person, with a Slack message when one is hot.
No lead sits in an inbox.
Stripe to your database
Signed Stripe webhooks update Supabase or Airtable: paid, refunded, cancelled. The same event arriving twice is handled once.
Your records match Stripe.
Zapier or Make, moved to n8n
Each flow rebuilt in n8n, run side by side with the old one until the results agree, then switched over.
Same work, a smaller bill.
The weekly report
Numbers from your CRM, payments, ads and spreadsheets, cleaned up and sent as one short summary to Slack or email.
Monday's report writes itself.
(04) What I build
What every workflow gets.So it runs without you watching.
Self-hosting done right
n8n on your server or cloud account with a database, backups, updates and HTTPS, owned by you.
Retries and alerts
Failed steps retry on their own, and a failed run reaches you on Slack or email with what went wrong.
Signed webhooks
Stripe and other webhooks checked for their signature, and safe when the same event arrives twice.
Secrets kept safe
API keys in n8n's credential store, never pasted into nodes, with the least access each one needs.
Notes in the workflow
Every workflow named and annotated, with a one-page note of what it does and what it touches.
A safe switch-over
The new workflow runs next to the old one until the results agree.
When a flow needs tests, long waits for approvals or careful failure handling, I'll say it belongs in code, and why. Most don't.
(05) How it works
Plan, build, run.Each one priced before it starts.
S/01Plan
Which flows to build or move first, hosting, where a person stays in the loop and what it costs to run. If I build it, the plan fee comes off the build.
$500 – $1,500
Quoted after a free call, a written plan in 3 to 5 days.
S/02Build
The workflows built and tested against your real data, then run beside the old setup until they agree.
$1,500 – $6,000
Quoted from the plan, agreed in writing before I start.
S/03Run
Workflows watched, n8n kept up to date, and fixes when a connected tool changes its API.
From $800 / month
Automations watched and tuned, plus fixes and updates. Cancel any month.
(06) What you keep
Your code, your accounts.Nothing held back.
Your repository
The code lives in a GitHub repository that's yours, with its full history: your own from the first commit, or one I set up and transfer to you. You can watch every change land.
Your accounts
Hosting, database, payments and app store accounts belong to you. If you have them, you invite me; if not, I set them up for the project and transfer each one to you at handover.
One engineer
The person on the first call is the person who writes the code. Nothing is handed to a junior or passed to another company.
A clean handover
Notes on how it works and how to deploy it, so you or any developer can carry on without me. Monthly plans cancel any month.
The code and designs are legally yours once each invoice is paid. Read the terms
(07) Proof
From my own work,so you can check it.
I chose the stack the hard way
At Unlok Insights I compared n8n, LangChain, LangGraph, the OpenAI tooling and AgentScope before picking what runs 9 workflows in production today.
Unlok InsightsDurable workflows, company-wide
I took Temporal from a proof of concept to company-wide at a fintech: onboarding, data ingestion and end-of-day jobs.
Read the post
(08) Read first
Free guideson the same problems.
- Migrating from Zapier to self-hosted n8n: what it costs and when it pays offWhen moving from Zapier to self-hosted n8n saves money, what running n8n yourself really involves, and how to switch without losing a run.
- Why no-code automations break at scale, and when to move them to codeZapier, Make and n8n are the right start for most teams. The signs an automation has outgrown them, and what moving it to code involves.
- Designing AI automations that touch money or customers: human-in-the-loop approval gatesHow to design AI automations you can trust with money and customers: approval gates, audit logs and spend limits, from building fintech systems.
(09) Questions
What founders askbefore we start.
Should I self-host n8n or use n8n Cloud?
n8n Cloud is simplest if you'd rather not run a server. Self-hosting costs less at volume and keeps your data with you, but someone has to keep it updated and backed up. The plan says which suits you, with the monthly cost of each.
Can you move my Zapier or Make workflows to n8n?
Yes. I rebuild each flow in n8n, run it next to the old one until the results agree, then switch it over, so no run is lost. Some flows are fine where they are, and the plan will say so.
How much does it cost?
The plan is $500 – $1,500, fixed, in a few days. Building is quoted from the plan, usually $1,500 – $6,000. If you go ahead within 30 days, the plan fee comes off the build, which is paid half upfront and half on handover.
Who owns the workflows and the server?
You do. You invite me to your n8n and hosting accounts, or I set them up and transfer them to you at handover. No shared passwords.
Something I haven't answered? Put it in your brief, or email me. I reply within a day. HS is one person, so the person you talk to is the one doing the work.