MyClawn n8n Workflows › Fix a workflow
Fix an n8n workflow error: what is wrong, where, and the corrected file
A workflow that ran for months stops on a Tuesday. The error names a node; the cause is three nodes earlier. Paste the workflow and the message, and see the diagnosis before you pay for the fix.
The errors we see most, and what is usually behind them
| What n8n shows | Usual cause | Fix |
|---|---|---|
| "The workflow has issues and cannot be executed" | A node has a required field that is empty or a credential that is not set, sometimes inside a sub-workflow | Find the node with the warning mark; fill the field or select the credential; save before running again |
| "Cannot read properties of undefined" | An expression expects a field that this item does not have | Point the expression at the right node and field, and give it a fallback for empty items |
| A node with a question mark after import | The file names a node type or version your n8n does not have, or a community node that is not installed | Replace it with the built-in node, or install the missing package |
| 401 or 403 from an app | The credential expired or lost a permission | Reconnect the account in n8n; check the scopes the node needs |
| 429 from an app | Too many calls too fast | Batch the items, add a wait between batches, turn on retry with a delay |
| Everything runs twice | The trigger fires twice for one event, or two copies of the workflow are active | A duplicate check on the event ID at the start; deactivate the copy |
| It runs, but an item is missing at the end | A node that continues on failure swallowed an error | Route the error output somewhere you will see it |
How to send us the workflow safely
- Open the workflow in n8n, select all nodes (Ctrl or Cmd + A) and copy them (Ctrl or Cmd + C).
- Paste them into the box together with the error message and what you expected to happen.
- Check one thing first: a copied workflow contains the names of your credentials, not the secrets. But an HTTP Request node that was imported from a cURL command can carry a key in its headers. Remove it before you paste.
You do not give us access to your n8n. The diagnosis is made from the file and the error message alone, which is enough for the causes in the table above.
Type what should happen, in plain words, or paste a workflow that is broken. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Draw my workflowWhat you get back
| File | What is in it |
|---|---|
| workflow.json | The corrected workflow, imported into n8n and checked before delivery. Your node names and layout are kept where possible |
| what-changed.md | Each change: which node, what was wrong, what it is now, and why |
| check-report.md | The n8n release it was imported into and the checks it passed |
| SETUP.md | What to reconnect after import, and how to test the fix with the pinned data |
A sample entry from what-changed.md:
Node: "Add row to sheet"
Was: {{ $json.customer.email }}
Now: {{ $('Tidy fields').item.json.email ?? '' }}
Why: after the Merge node the item no longer has a "customer" object, so the
expression failed on every order without an account. It now reads the
email from the node that always has it and falls back to an empty value.What we cannot fix from a file
- A server problem: n8n out of memory, a queue that is stuck, a broken update. That needs someone on your server.
- A problem inside the other app: a deleted field, a closed account, a plan limit.
- Errors that only appear with data we cannot see. Send one example item with the private parts replaced, and we can.
Questions
Does a fix count as a workflow on my plan?
Yes, one. It includes two rounds of changes, so if the corrected file meets another error on your real data, send that error too.
Can you fix a workflow built by someone else?
Yes. Most of the ones we expect are: built by a freelancer who is gone, or generated by a chatbot.
Will you rebuild it from scratch?
Only if you ask. The default is the smallest change that fixes the cause, so you still recognise your workflow.
Type what should happen, in plain words, or paste a workflow that is broken. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Draw my workflowMore about n8n Workflows
Sources (checked 2026-11-13): docs.n8n.io/build/manage-workflows/export-and-import · www.upwork.com/jobs/~022120951956341167610 · www.npmjs.com/package/n8n