I will fix, debug or build your n8n workflow and automation


About this gig
Your n8n workflow runs fine in the editor and breaks in production. That is the part I fix.
I run self-hosted n8n in production, including a WhatsApp AI ordering agent that handles real customers every day. The workflow is public on my GitHub, so you can inspect how I build before you hire me.
WHAT I FIX MOST OFTEN
- Webhooks that get verified but never receive a payload
- Nodes that work on one item and break on a list, because the loop was missed
- Credentials and OAuth that expire silently and take the automation down
- Missing error branches, so one bad record kills the whole run
- Rate limits and timeouts that only appear under real volume
- AI agent nodes that return prose instead of parseable JSON
WHAT I BUILD
API integrations, HTTP request nodes with proper auth, database reads and writes, scheduled jobs, human approval steps, alerts to Slack, Telegram or email.
You get the fixed workflow as an importable JSON, plus a written note explaining what was wrong and why. If the cause turns out to be outside n8n, I tell you straight away instead of billing for guesswork.
I never ask for your password or 2FA code. You add me as a user, or we work over screen-share with you in control.
Get to know Alexandre T.
AI Automation and Full Stack Developer
- FromBrazil
- Member sinceOct 2022
Languages
Portuguese, English
FAQ
Can you work on n8n Cloud, or only self-hosted?
Both. I run self-hosted n8n myself, and I work on Cloud instances just as often.
Do you need my credentials?
No. You add me as a user on your instance, or we do a screen-share with you driving. I never take passwords or 2FA codes.
My workflow works on Test but fails on schedule. Why?
Almost always execution context: test runs one item, production runs a list, or a credential works interactively and not headless. That is a Basic package fix.
Can you connect n8n to a tool that has no native node?
Yes, through the HTTP Request node. If the service has an API, it can be integrated.
