I will audit your n8n automation for reliability, error handling and handover


About this gig
You have automations nobody has looked at since the day they were built. They are probably fine. The problem is you cannot tell, and neither can whoever inherits them.
The failures that cost money are the quiet ones. A webhook stops firing and nothing complains. A retry posts the same order twice. A credential rotates and one branch fails silently for a fortnight.
WHAT YOU GET, ON EVERY ORDER
A dependency map of what calls what. A failure-risk register of every place your workflows can fail without telling you, classified by whether it loses data, duplicates data, or just stops. A prioritised backlog, estimated in hours, that you can hand to any developer, including one who is not me. And a list of what someone covering for you could not work out. Fixed examination, fixed deliverable. I am not selling a verdict, and I will not invent problems that are not there.
WHAT I CHECK FOR
The failure classes I audit are the ones I built into my reference pipeline: duplicate suppression, replayable dead letter queues, unbounded state, credential handling and whether anything notices silence.
github.com/benfoster1997/n8n-portfolio
Self-initiated demonstration projects, not client work.
Get to know Ben Foster
Ai Autonomous Engineering
- FromUnited Kingdom
- Member sinceJul 2026
- Avg. response time1 hour
Languages
English
My Portfolio
FAQ
What if you find nothing wrong?
Then you get a written report saying so, with the evidence, and you can show it to whoever needed convincing. That is a legitimate outcome and it is priced in. I will not manufacture findings to justify the fee, and anyone who guarantees they will find problems is telling you something.
Do you fix what you find?
Not at Basic or Standard — those are review only, deliberately, so the report is honest rather than a sales document. Premium implements the single highest-risk item, with tests and a runbook, plus a recheck 30 days later. Anything else is quoted separately from the same backlog.
Do I have to give you access to my live system?
No. Exported workflow JSON with credentials stripped is enough for the whole Basic audit. If you would rather redact node names too, say so and I will work around it. Read-only access speeds things up but is never required.
My workflows are in Make or Zapier, not n8n. Can you still audit them?
Yes, if you can export or screenshot the full scenario. The failure classes are identical across tools — duplicates, silent drops, unbounded state, credential handling. Message me first so I can confirm the export format before you order.
Something is broken right now. Is this the right gig?
Probably not. An audit is a scheduled examination, not incident response, and buying one while a system is down wastes your money and my delivery clock. Message me and I will tell you straight whether you need a fix, an audit, or neither.

