Most n8n workflows don’t break. They stop, quietly, and nobody notices for three weeks.
A monitoring script whose underlying command was renamed keeps succeeding at checking nothing. A mail watcher points at the inbox while the messages that mattered are being auto-filed into Trash. On the dashboard, “healthy” and “did nothing” look identical.
That’s what I fix, and it’s all I sell.
What you get - 5 working days, 1500 EUR fixed, 50% up front:
- A written diagnosis of your three most expensive processes, quantified from your numbers, not my estimates.
-
- One workflow delivered to production - the most profitable of the three, not all three.
-
- Delivered with retries, a dead-letter queue, error branches, failure alerting and a runbook, so when it breaks at 3am you know, and you know what to do.
-
- 30 days of correction included on that workflow.
- Guarantee: if the diagnosis doesn’t find at least 5 hours a week to give you back, I say so and you pay nothing.
- Public code, with tests, before you talk to me:
-
- GitHub - remten341/n8n-resilient-workflow: Production n8n workflow with retries, dead-letter queue, error branches and alerting. 21 nodes, 19 connections, importable JSON. · GitHub - 21 nodes, retries, dead-letter queue, alerting, importable JSON
-
- GitHub - remten341/multi-llm-gateway: Multi-provider LLM gateway with automatic failover, circuit breaker and hard spend caps. Pure stdlib Python, injectable transport, 43 tests. · GitHub - provider failover, circuit breaker, hard spend caps, 43 tests
-
- GitHub - remten341/rag-freshness-gating: Hybrid RAG pipeline (BM25 + vector, RRF) with document freshness gating and metadata pre-filtering. 54 tests, sample corpus included. · GitHub - hybrid BM25 + vector retrieval with staleness gating, 54 tests
- I run this stack daily on my own infrastructure: two machines, self-hosted n8n, PostgreSQL, 64 supervised services, multi-provider LLM routing with per-agent spend caps and a kill-switch that trips before the bill does.
- Async by default, no discovery call required. Tell me the process that’s costing you the most and I’ll tell you honestly whether it’s worth automating.