I will fix, debug or improve your n8n workflow

A
aijidokalab
A
aijidokalab
Taku
fix, debug or improve your n8n workflow
Full Screen
fix, debug or improve your n8n workflow

About this gig

n8n workflow throwing errors? Stuck on "not valid JSON"? Credentials look connected but nothing runs?


I've hit and fixed the classic n8n traps in production:

Expression-mode JSON bodies that break HTTP Request nodes

Object-shaped email fields that crash downstream nodes ("input.split is not a function")

Notification loops that make workflows trigger themselves

AI nodes returning unparseable output

Rate limits (429) killing runs and how to retry gracefully


Send me your workflow export (JSON) and a description of what should happen. I'll find the problem, fix it, and explain the why in plain English so it doesn't bite you again.


Fast, small, no drama. If your problem turns out to be bigger than a fix, I'll tell you honestly before any extra cost.


I don't work on workflows that scrape sites against their terms or automate platforms that prohibit automation.

  • AI engine

    • GPT
    • Llama
    • Claude

  • Programming language

    • JavaScript
    • Python

Get to know Taku

Taku

n8n and AI Automation Specialist

  • FromJapan
  • Member sinceJul 2026

  • Languages

    Japanese, English
I build and run AI-powered automations for my own business every day — a Gmail inquiry-handling assistant that sorts, labels and drafts replies, a cold-outreach pipeline, and a YouTube content automation. Now I build the same kind of n8n workflows for clients: email triage, AI reply drafts, data entry, alerts and reports. Everything is designed so the AI drafts and a human approves — nothing is ever sent automatically, and I never ask for your passwords (you connect your own accounts via official OAuth). Every delivery includes plain-English documentation and a walkthrough video.

Related tags