You will get your Zapier or Make.com automations migrated to self-hosted n8n
Project details
Zapier and Make are excellent until the invoice arrives. Task-based pricing punishes you exactly when the automation starts working - the more it runs, the more you pay.
n8n does the same job on your own server for the cost of the server. But a migration is not copy and paste. Zapier hides retries, delays and field mapping behind a friendly screen, and those details are what break silently after the switch.
I run 31 live n8n workflows and 123 scheduled jobs on my own servers, so I have already hit most of the traps: OAuth tokens that expire quietly, webhook URLs that must be re-registered, timezone drift on schedules, and error branches the original Zap never had.
Starter - up to 3 Zaps or scenarios.
Standard - up to 8, including branching, filters and error handling.
Full - up to 15, plus failure alerts to email, Slack, Telegram or Discord.
Every migrated workflow runs side by side with the original before you switch anything off, so you can compare the output yourself.
You keep your own credentials. I never ask for passwords or API keys - you connect the accounts inside your own n8n.
n8n does the same job on your own server for the cost of the server. But a migration is not copy and paste. Zapier hides retries, delays and field mapping behind a friendly screen, and those details are what break silently after the switch.
I run 31 live n8n workflows and 123 scheduled jobs on my own servers, so I have already hit most of the traps: OAuth tokens that expire quietly, webhook URLs that must be re-registered, timezone drift on schedules, and error branches the original Zap never had.
Starter - up to 3 Zaps or scenarios.
Standard - up to 8, including branching, filters and error handling.
Full - up to 15, plus failure alerts to email, Slack, Telegram or Discord.
Every migrated workflow runs side by side with the original before you switch anything off, so you can compare the output yourself.
You keep your own credentials. I never ask for passwords or API keys - you connect the accounts inside your own n8n.
Programming Languages
JavaScript, Python, TypeScriptCoding Expertise
Performance OptimizationWhat's included
| Service Tiers |
Starter
$150
|
Standard
$350
|
Advanced
$600
|
|---|---|---|---|
| Delivery Time | 7 days | 12 days | 18 days |
Number of Revisions | 1 | 2 | 2 |
Install Script | - | - | - |
Test Script | |||
Task Automation |
Frequently asked questions
About Duc
n8n & Self-Hosted AI Automation Engineer | Zero-API-Cost Pipelines
Vo Xu, Vietnam - 9:16 am local time
For the past two years I have been running a fully self-hosted content and media automation stack, alone, end to end:
- 31 live n8n workflows orchestrating crawling, content generation, image generation, publishing and monitoring
- 123 scheduled jobs and services across 4 Linux/macOS servers, with a supervisor agent that reports system health to a chat channel every day
- A news pipeline that crawls 70+ active sources, deduplicates near-identical stories across outlets, runs quality and fact-check gates, generates original images, and publishes to a live website unattended, four times a day
- Self-hosted LLMs (14B + 35B) served locally behind an internal gateway with queueing, rate limiting and fallback, so the whole system runs at zero API cost
- Local image generation (FLUX) with a full asset pipeline: WebP/AVIF variants, CDN delivery, checksum deduplication, orphan cleanup
- A publisher that takes one video and distributes it to Facebook, YouTube and TikTok with platform-appropriate metadata
What I am good at, specifically:
- Cutting LLM API bills to near zero by moving workloads to self-hosted models, and routing only what genuinely needs a frontier model to a paid API
- Building content pipelines that do not produce garbage: deduplication, quality gates, fact-checking against the source material, and human approval steps where they matter
- Making automations observable. If a job dies at 3am you get a message, not a silent gap in your data
- Rescuing automations that worked in testing and fall over in production
Stack: n8n, Node.js, Python, PostgreSQL (+pgvector), Redis, Docker, systemd, local LLM serving on Apple Silicon and NVIDIA GPUs, Directus, Astro, Cloudflare (Pages, R2, Workers), Facebook Graph API, YouTube and TikTok APIs, Synology.
A note on how I work: I am based in Vietnam and I prefer asynchronous, written collaboration - written briefs, chat, screen recordings and clear documentation - over daily video calls. My spoken English is basic. If your project needs a lot of live conversation, I am probably not your best fit. If you want someone who ships and documents what he shipped, I am.
Tell me the process you are tired of doing by hand, and I will tell you honestly whether automating it is worth your money.
Steps for completing your project
After purchasing the project, send requirements so Duc can start the project.
Delivery time starts when Duc receives requirements from you.
Duc works on your project following the steps below.
Revisions may occur after the delivery date.
Map what you actually have
I read every Zap or scenario end to end and write down the trigger, the filters, the field mapping and the failure paths. You get that map before I build anything.
Rebuild in n8n, one at a time
Each workflow is rebuilt and run against real data, not a dummy payload. You connect your own credentials inside your own n8n - I never hold your keys.