You will get your broken n8n workflow fixed, with the real root cause explained
Project details
Your n8n workflow worked in testing. Then it broke in production - or worse, it stopped producing results without throwing a single error. I fix both kinds. The second kind is what I am actually good at.
Most automations do not crash. They quietly stop producing while every dashboard stays green. I run a self-hosted pipeline with 31 live n8n workflows and 123 scheduled jobs across 4 servers, and I have been burned by exactly this: a job that had been dead for weeks while the monitoring reported zero alerts.
Diagnosis ($45): send me your workflow JSON and a failed execution. You get a written report - what is failing, why, and the exact fix. No access to your account or server. Nothing I do can break what you are running.
Diagnosis + Fix ($120): plus a corrected workflow JSON that you import yourself, tested against your sample data.
Fix + Watchdog ($250): plus a monitoring workflow that alerts you when it fails AND when it silently returns nothing.
I work asynchronously - written briefs and documentation rather than live calls. My spoken English is basic; my written English is not.
Not sure which tier? Message me first and I will tell you honestly.
Most automations do not crash. They quietly stop producing while every dashboard stays green. I run a self-hosted pipeline with 31 live n8n workflows and 123 scheduled jobs across 4 servers, and I have been burned by exactly this: a job that had been dead for weeks while the monitoring reported zero alerts.
Diagnosis ($45): send me your workflow JSON and a failed execution. You get a written report - what is failing, why, and the exact fix. No access to your account or server. Nothing I do can break what you are running.
Diagnosis + Fix ($120): plus a corrected workflow JSON that you import yourself, tested against your sample data.
Fix + Watchdog ($250): plus a monitoring workflow that alerts you when it fails AND when it silently returns nothing.
I work asynchronously - written briefs and documentation rather than live calls. My spoken English is basic; my written English is not.
Not sure which tier? Message me first and I will tell you honestly.
Programming Languages
JavaScript, Python, TypeScriptCoding Expertise
Performance OptimizationWhat's included
| Service Tiers |
Starter
$45
|
Standard
$120
|
Advanced
$250
|
|---|---|---|---|
| Delivery Time | 3 days | 5 days | 7 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 - 4:59 pm 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.
Read and reproduce
I go through your workflow JSON and the failed execution, and reproduce the failing behaviour on my own n8n. No access to your account or server is needed.
Find the root cause
I isolate what is actually breaking and write it up in plain language: what fails, why it fails, and the exact change that fixes it. This report is yours even if you stop here.