I will debug and fix your broken n8n workflow from a json export


About this gig
Your n8n workflow used to run and now it fails, loops, skips items, or throws an error you can't read? Send me a sanitized JSON export and I will find the cause and fix it - without any access to your instance.
WHAT YOU GET
- the fixed workflow as an importable JSON file
- - a short failure report: what broke, why, and what changed (node by node)
- - a test run on mock data with screenshots: happy path + the error case
- - a re-import note: which credentials to re-attach and what to verify
HOW IT WORKS: export the workflow (three-dot menu > Download - n8n strips credentials by default), paste the error text or a screenshot, and describe what it should do. I reproduce the failure locally, fix it, and send everything back.
PACKAGES: Basic = one failing node or branch. Standard = fix + hardening (error workflow, retries, alert on failure). Premium = fix + hardening + cleanup and documentation of the whole workflow.
NOT INCLUDED: hosting, deploying on your account, credentials setup, installing community nodes on your server.
AI-assisted, human-reviewed: every delivery is built for your specific workflow and checked by a senior engineer before it ships.
Get to know Sergey Y
Senior Software Engineer, Automation, AI Agents and Web Apps
- FromRomania
- Member sinceSep 2026
- Avg. response time1 hour
Languages
English, Ukrainian, French
Other Software Development Services I Offer
FAQ
Do you need access to my n8n?
No. I work only from your JSON export and rebuild the failure locally on mock data. You re-attach credentials after import (takes 2-5 minutes).
Cloud or self-hosted?
Both. Tell me your n8n version; I test on the same major version.
My workflow uses community nodes. Is that a problem?
If the node installs from npm and is in your export, fine. Custom or private nodes need a custom offer first.
Can you fix it live on my server?
Not within this gig - it deliberately avoids access to your systems. You import the fixed JSON yourself with the re-import note.
How do I know the fix works?
Every delivery includes a documented mock-data run: screenshots of the successful execution and of the handled error case.
What counts as one revision?
One consolidated list of defects against the frozen spec we agree on before I start. New features or a different failure are a new order.

