I will diagnose or fix an error in your n8n or make workflow


About this gig
Leads disappear. Records appear twice. A workflow stops after an API error, and you only notice days later.
I investigate and repair a specific problem in an existing n8n workflow or Make scenario, with checks against real examples of the expected behaviour.
Typical requests:
- Duplicate processing after retries or repeated webhooks
- Missing fields, broken mappings or failed filters
- API errors, pagination or rate-limit handling
- Failures that need a clear error path or notification
Message me before ordering with the failing step, a redacted execution log and the expected result. I will confirm scope before you purchase.
DIAGNOSE: investigate one issue and provide findings and a repair plan. No workflow changes included.
FIX: repair one agreed issue in one workflow and test the affected path.
FIX + TEST: add agreed repeat-event and failure checks, plus a short walkthrough.
Repair packages include the workflow export or change instructions, test evidence and handover notes.
Start with a sanitised export or test copy. New workflows, extra integrations and ongoing monitoring need a separate scope.
Get to know Tom T
Oxford maths graduate, app and automation repairs
- FromUnited Kingdom
- Member sinceSep 2026
- Avg. response time1 hour
Languages
English, French
FAQ
Can you fix duplicates or missing records?
Often these come from retries, repeated events, mapping errors or incomplete API responses. I first inspect the workflow and execution evidence, then confirm a repair scope and test cases. The affected service must support the access and operations the repair requires.
Does Basic include changing my workflow?
No. Basic is investigation and a written repair plan for one issue. Standard and Premium include a repair after we agree the scope. This keeps an unknown problem from becoming an open-ended project.
What access will you need?
We can start with a sanitised workflow export, redacted execution logs and sample input/output. If connected testing is needed, we will agree collaborator access and test destinations. Please do not send account passwords, API keys or tokens in messages or files.
Will tests send emails or create real records?
We agree safe test destinations first, such as a test inbox, sandbox CRM or staging database. Production actions are not run without explicit agreement. Any service usage charges remain the buyer's responsibility.
Do you build new automations or monitor them permanently?
These packages repair an existing workflow. New integrations, a replacement workflow and ongoing monitoring require a separate scope. Handover explains the checks and any remaining service limits.
What does one revision cover?
One round of corrections to the agreed repair and acceptance checks. A new integration, additional workflow or changed business rule is a separate request.
