n8n - 💡(How to fix) Fix HTTP Request node in some cases fails to display details for the 400 Bad Request response

Bug Description

When the HTTP Request node is configured to continue on error, and a 400 Bad Request status is returned from a server, its output panel only shows the generic

[
  {
    "error": {
      "message": "Bad request - please check your parameters",
      "timestamp": 1778581582757,
      "name": "NodeApiError",
      "description": "Bad Request",
      "context": {}
    }
  }
]

but no Error details with From HTTP Request section that would be shown otherwise. This doesn't just make the debugging harder by hiding the reason of the response, but in fact obscures that there were are any useful data at all provided with it.

The description field of the generic message above might display the returned json as a string - truncated. Or not at all if the returned json contains an "error" string which then takes its place as in the example above.

To Reproduce

1. Configure a Webhook-Respond pair returning code 400 and

{
  "error": "Bad Request"
}

as the response body and run it. 2. Create a HTTP Request node and choose Continue for its On Error dropbox. 3. Run HTTP request

Expected behavior

The full response data is accessible for inspection in some way at all times.

Debug Info

Operating System

Windows 22H2

n8n Version

2.18.5

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted