Route HTTP errors instead of stopping
An integration calls a partner endpoint that occasionally returns HTTP 500 responses. Today the whole workflow stops when the request fails, so downstream reporting never runs.
You'll import a starter that hits a test URL returning 500, switch the HTTP Request node to Continue Using Error Output, then add an Edit Fields branch that records the failure so you can audit errors without aborting the run.
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