I will fix and optimize your broken n8n automation workflow

P
purdea_mihai
P
purdea_mihai
Purdea Mihai

About this gig

Your workflow passed testing and died at real volume. I fix that.


I run n8n in production every day for my own B2B agency, not as a hobby. Three failures I have diagnosed and fixed on live systems:


Out-of-memory crashes from a splitInBatches loop holding every item in memory. Removed the loop, capped records per run.


n8n writing the integer 1 into a status column where everything downstream compared against a string. Every comparison failed silently and records were skipped with no error raised.


A scheduler counting calendar days instead of business days, firing actions on weekends.


Two of those three raised no error at all. That is why "it looks like it works" is not the same as working.


What you get:

- The fault diagnosed, not guessed at

- The fix implemented and tested on your data

- Written explanation of why it broke

- The workflow JSON and a video walkthrough


I also work with Google Apps Script, Gemini and OpenAI APIs, Apify, and Google Workspace APIs.


Message me with what is broken before ordering. If I cannot fix it, I will tell you.


Get to know Purdea Mihai

Purdea Mihai
  • FromRomania
  • Member sinceApr 2024
  • Languages

    English, German
I build automation systems that keep running after the demo. I run the outbound infrastructure for my own B2B agency: n8n pipelines for scraping, qualification and AI enrichment, Apps Script scheduling sends across twelve authenticated inboxes, and a reply tracker resolving thread status across all of them. It runs daily, and I fix it when it breaks. That shapes how I build. Most automations fail in week ten, not week one, and usually without raising an error. I build against the silent failures. Tell me what is broken and I will tell you honestly whether I can fix it.

My Portfolio

Other AI Development Services I Offer