n8n - 💡(How to fix) Fix HTTP Calls not working [2 comments, 2 participants]

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…
GitHub stats
n8n-io/n8n#28596Fetched 2026-04-17 08:54:43
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
commented ×2closed ×1labeled ×1mentioned ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

Error messages include "Invalid JSON in response body". "Unsupported content type: text/html; charset=UTF-8" and so on.

  • error: all

Fix Action

Fix / Workaround

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
{
  "nodes": [
    {
      "parameters": {
        "method": "PATCH",
        "url": "=https://limitless-services.simprosuite.com/api/v1.0/companies/{{ $json.body.Company }}/jobs/{{ $json.body.JobID}}",
        "authentication": "genericCredentialType",
        "genericAuthType": "oAuth2Api",
        "sendBody": true,
        "bodyParameters": {
          "parameters": [
            {
              "name": "Status",
              "value": "={{ 852 }}"
            }
          ]
        },
        "options": {}
      },
      "id": "f129ae19-59bd-418c-9bf8-7094d45b88e2",
      "name": "Job Status: Confirmed",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.4,
      "position": [
        1152,
        96
      ],
      "credentials": {}
    }
  ],
  "connections": {
    "Job Status: Confirmed": {
      "main": [
        []
      ]
    }
  },
  "pinData": {},
  "meta": {
    "instanceId": "523402ce26df83126eba14dcbc172ac4d679507f8bebf6baabc468a10a8849bb"
  }
}

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
{
  "nodes": [
    {
      "parameters": {
        "method": "PATCH",
        "url": "=https://limitless-services.simprosuite.com/api/v1.0/companies/{{ $json.body.Company }}/jobs/{{ $json.body.JobID}}",
        "authentication": "genericCredentialType",
        "genericAuthType": "oAuth2Api",
        "sendBody": true,
        "bodyParameters": {
          "parameters": [
            {
              "name": "Status",
              "value": "={{ 852 }}"
            }
          ]
        },
        "options": {}
      },
      "id": "f129ae19-59bd-418c-9bf8-7094d45b88e2",
      "name": "Job Status: Confirmed",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.4,
      "position": [
        1152,
        96
      ],
      "credentials": {}
    }
  ],
  "connections": {
    "Job Status: Confirmed": {
      "main": [
        []
      ]
    }
  },
  "pinData": {},
  "meta": {
    "instanceId": "523402ce26df83126eba14dcbc172ac4d679507f8bebf6baabc468a10a8849bb"
  }
}
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

I had several automations fully functional before I upgraded yesterday. I upgraded my plan, then copied one workflow into a new project, changed the credentials and now both are failing on the HTTP request nodes. If I create a new workflow and add a HTTP node it works fine, but all my existing workflows are showing errors regarding the response. They are not receiving a JSON even when I make the exact same call in a new workflow outside of those projects. This is hours of work to rebuild them from scratch and frustrating enough to make me reconsider moving to another service.

What is the error message (if any)?

Error messages include "Invalid JSON in response body". "Unsupported content type: text/html; charset=UTF-8" and so on.

Please share your workflow/screenshots/recording

<img width="1981" height="1271" alt="Image" src="https://github.com/user-attachments/assets/7ca55c40-84e4-4247-ad9c-d31b02982224" /> <img width="1981" height="1271" alt="Image" src="https://github.com/user-attachments/assets/58a507cd-b70a-46bc-b118-7584303372f4" />
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
{
  "nodes": [
    {
      "parameters": {
        "method": "PATCH",
        "url": "=https://limitless-services.simprosuite.com/api/v1.0/companies/{{ $json.body.Company }}/jobs/{{ $json.body.JobID}}",
        "authentication": "genericCredentialType",
        "genericAuthType": "oAuth2Api",
        "sendBody": true,
        "bodyParameters": {
          "parameters": [
            {
              "name": "Status",
              "value": "={{ 852 }}"
            }
          ]
        },
        "options": {}
      },
      "id": "f129ae19-59bd-418c-9bf8-7094d45b88e2",
      "name": "Job Status: Confirmed",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.4,
      "position": [
        1152,
        96
      ],
      "credentials": {}
    }
  ],
  "connections": {
    "Job Status: Confirmed": {
      "main": [
        []
      ]
    }
  },
  "pinData": {},
  "meta": {
    "instanceId": "523402ce26df83126eba14dcbc172ac4d679507f8bebf6baabc468a10a8849bb"
  }
}

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.13.3
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-16T23:53:57.402Z

extent analysis

TL;DR

The most likely fix is to update the HTTP request nodes in the affected workflows to handle the new response content type or to verify the API endpoint and credentials.

Guidance

  • Verify that the API endpoint https://limitless-services.simprosuite.com/api/v1.0/companies/{{ $json.body.Company }}/jobs/{{ $json.body.JobID}} is correct and functional, as the error messages suggest an issue with the response content type.
  • Check the credentials used in the HTTP request nodes, as the issue started after changing credentials in the new project.
  • Inspect the response from the API endpoint using a tool like Postman or cURL to confirm the content type and JSON structure.
  • Consider updating the HTTP request nodes to handle the text/html content type or to specify the expected JSON content type in the request headers.

Example

No code example is provided, as the issue is related to the API endpoint and credentials rather than a specific code snippet.

Notes

The issue may be related to changes in the API endpoint or credentials after the plan upgrade and project changes. It's essential to verify the API endpoint and credentials to resolve the issue.

Recommendation

Apply a workaround by verifying the API endpoint and credentials, and update the HTTP request nodes accordingly, as the root cause of the issue is likely related to these changes.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING