Home › Hire an n8n Freelancer
HireHire an n8n freelancer — remote, Philippines-based, everything documented
13+ n8n workflows in production, every one published with a node-by-node walkthrough you can read before you hire me. Ten years of enterprise automation before that. Below: what I build, how engagements work, and a checklist for vetting any n8n developer — including me.
At a glance
- Available: project-based, part-time or retainer. Remote, working with US, UK, AU and CA clients.
- Structure: fixed-price milestones from around $300. You know the number before work starts.
- Proof: the workflows are public on GitHub with written walkthroughs — read the code before you talk to me.
- Included: node-by-node walkthrough, Loom, error handling from day one, 7-day fix guarantee.
How to vet an n8n freelancer
Apply this to anyone you're considering. It separates people who have run automation in production from people who have built demos, and it takes about four minutes.
- "Show me a real workflow, not a screenshot." A canvas screenshot proves nothing — anyone can arrange nodes. Ask for the exported JSON or a walkthrough of what each node does and why. Vagueness here is the single strongest signal.
- "What happens when a node fails at 3am?" The correct answer involves an error workflow, a notification, and a retry policy. The wrong answer is "it would show in the executions list." Silent failure is the actual risk with automation, not bad output.
- "How do you hand it over?" You want written documentation you own. If handover is a call and a login, you've bought a dependency rather than a system.
- "What would you refuse to automate?" Anyone who says "nothing" is selling. Real answers: processes that change weekly, anything where a wrong output is unrecoverable, anything that would take longer to maintain than to do by hand.
- Check they've hit the boring walls. Rate limits, pagination, API version headers, memory limits on small instances, credentials that expire. Someone who has shipped will have opinions about at least two of these.
My answers, since I just set the test
Real workflows: all public on GitHub with walkthroughs. Failure at 3am: a shared error-handler workflow is wired across every build in the fleet — it catches the failure and notifies rather than dying quietly. Handover: a written node-by-node walkthrough plus a Loom, every time. Would refuse: anything where an AI getting it wrong is unrecoverable and unreviewed — money moving, or a message going out that can't be taken back, without a human in the loop.
What I build in n8n
| Area | Examples from the public portfolio |
|---|---|
| Voice & chat agents | AI voice front desk (Twilio + Vapi, books into real calendars), multi-tenant chat front desk on GoHighLevel, WhatsApp and Telegram agents |
| Lead response | Speed-to-lead capture, scoring and routing; email and WhatsApp lead qualifiers; CRM lead engine |
| Documents & knowledge | RAG support chatbot over a business's own files; call transcripts turned into written, priced proposals; document extraction into clean records |
| Back office | Accounts-receivable chasing with cash-flow briefs; hiring and onboarding pipelines; task relay from chat into project tools; email triage |
| Intelligence & reporting | Competitor monitoring, market digests, job-feed scoring, weekly owner reports that build and send themselves |
| Reliability | A shared error-handling workflow wired across the whole fleet — the piece most portfolios don't have |
Full list, with the walkthroughs, on GitHub.
Working with me
Timezone
Manila is GMT+8. That's near-full overlap with Australia and Singapore, comfortable overlap with the UK in my afternoon, and early-morning Manila covers US evenings and West Coast afternoons. My enterprise delivery work ran across the US, Singapore and the Philippines simultaneously, so scheduled overlap is normal practice rather than a special arrangement.
Engagement shapes
- Fixed-price build — a defined system, quoted as milestones. Best for anything with a clear outcome.
- Retainer — ongoing changes, monitoring and new workflows for a business already running automation.
- Audit — one process, an honest answer on whether automation is worth it. Free for the first one.
What I'll tell you not to do
Automating a broken process makes a faster broken process. Occasionally the right answer is a template, a settings toggle you already own, or hiring a person. You'll get that answer before an invoice rather than after.
Common questions
Self-host n8n or use n8n Cloud?
Self-hosting is cheaper and gives you full control — it's what I run. But it needs someone to own the instance, and small instances need memory-conscious design (heavy AI nodes will exhaust a small box; the fix is usually calling the model over HTTP instead). If nobody technical is around, cloud is the honest recommendation even though it costs more.
Can you take over an existing n8n setup?
Yes. Usually it starts with an audit: what's running, what's silently failing, and what has no error handling. That last one is almost always the finding.
Do you work with Make or Zapier too?
Yes, and I'll tell you when one of them is the better fit. Some builds run across all three — a real one of mine uses Make for the realtime path and Zapier for record-keeping, because each was better at its half.
Do you have client reviews?
Not yet — I'm early into freelance work after a decade in enterprise delivery, and I'd rather say that plainly than imply otherwise. What I offer instead is verifiable: the workflows are public, the walkthroughs are readable, and the enterprise track record is on LinkedIn. Judge the work directly.
Tell me what's eating the hours
One process, plain English. You'll get back what could be automated, roughly what it would cost, and an honest read on whether it's worth doing. No charge, no call required.