n8n - 💡(How to fix) Fix update to 2.19.5

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

NodeApiError: config.headers.setContentType is not a function

Fix Action

Fix / Workaround

After the upgrade to n8n Cloud 2.19.5, HTTP Request nodes fail before sending the request.

Code Example

config.headers.setContentType is not a function

---

NodeApiError: config.headers.setContentType is not a function
RAW_BUFFERClick to expand / collapse

HTTP Request node broken after update to n8n Cloud 2.19.5

Describe the problem/error/question

After the upgrade to n8n Cloud 2.19.5, HTTP Request nodes fail before sending the request.

The issue happens with:

  • old HTTP Request nodes
  • newly created HTTP Request nodes
  • Authentication = None
  • manual headers
  • JSON headers
  • "Using Fields Below" headers

The request never reaches the API endpoint.

The problem started immediately after the cloud update.


What is the error message (if any)?

config.headers.setContentType is not a function

Stack trace references:

NodeApiError: config.headers.setContentType is not a function

Please share your workflow/screenshots/recording

Minimal reproduction:

HTTP Request node:

Headers:

  • Authorization: Bearer sk-xxxxx
  • OpenAI-Beta: assistants=v2

The same error also happens with:

  • Content-Type removed
  • simple GET requests
  • newly created HTTP Request nodes

Environment:

  • n8n Cloud
  • version: 2.19.5

Expected behavior

HTTP Request node should execute normally and send the request.


Additional information

The issue seems related to internal header handling in the HTTP Request node/runtime.

The error occurs before the request is sent.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

HTTP Request node should execute normally and send the request.


Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix update to 2.19.5