Route HTTP errors instead of stopping
This workflow calls an API that sometimes answers with HTTP 500. Out of the box, n8n stops the whole run right there — so you capture nothing useful and anything downstream never fires.
Import the starter, set HTTP Request to Continue Using Error Output, and route the red error path into Edit Fields so failures get logged without killing the execution.
This exercise is part of the course
Intermediate Workflow Automation with n8n
Hands-on interactive exercise
Turn theory into action with one of our interactive exercises
Start Exercise