//n8n pitfalls · high
Error Trigger workflow must be separate
The Error Trigger node must be in a SEPARATE workflow from the one being monitored. It cannot catch errors in its own workflow. Create a dedicated error-handling workflow with an Error Trigger, then set each production workflow to use it via Settings > Error Workflow.
- Category
- n8n_general
Source: the n8n-mcp pitfall list, maintained by the tool's author
Mistakes AI agents make in n8n
- Execute Workflow + Wait nodes cause data loss
- SplitInBatches + Wait nodes cause state loss
- Never use append on sheets with formula columns
- $env expressions blocked in Code nodes
- saveExecutionProgress fills disk space
- IF node uses branch true/false not sourceIndex
- Code node $input.all() vs $input.first()
- Per-item execution on large datasets
- Webhook node response must be sent explicitly
- $getWorkflowStaticData global loses data in loops