N8N Automation Interview Questions
Prepare for automation engineer roles. Master webhooks, nodes, conditionals, and API integrations.
Editorial Integrity
Sourced from real N8N certification tracks and enterprise automation teams.
How do you handle errors in an n8n workflow?
You handle errors by configuring the 'On Error' behavior of individual nodes (e.g., 'Continue On Fail') or by creating a dedicated Error Trigger workflow that catches all failed workflow executions.
Deep Dive Explanation
In production automation, APIs will inevitably fail or timeout. n8n provides multiple ways to handle this. You can click into a specific node's settings and set 'On Error' to 'Continue On Fail'. This allows the workflow to keep running and gives you an `$error` object to route through an IF node. Alternatively, for global monitoring, you can create a separate workflow starting with an 'Error Trigger' node. When any of your main workflows fail, this error workflow is triggered, allowing you to send an alert to a Slack channel with the exact execution ID and error message.
Leaving default error settings, causing a workflow to stop executing entirely when a non-critical API (like sending a summary email) fails.