Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Import cURL function in HTTP Request node doesn't handle integers in Json values. [4 comments, 4 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#29394•Fetched 2026-04-29 06:35:10
View on GitHub
Comments
4
Participants
4
Timeline
19
Reactions
0
Author
lopatoidlopatoid
Participants
bharat3214bharat3214lopatoidlopatoidn8n-assistant[bot]n8n-assistant[bot]tcurdttcurdt
Timeline (top)
mentioned ×6subscribed ×6commented ×4labeled ×3

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When I execute in the terminal curl 'http://hostname' -H 'content-type: application/json' --data-raw '{"size":100}', that's what I get on the server: {"size":100} When I go into the HTTP Request node, click Import cURL and execute the node, that's what I get: {"size":"100"} They are not the same; the number was converted to a string while importing. I know about {{parseInt(100)}} trick, but Import cURL function should also know about it.

To Reproduce

  1. Go to HTTP Request node
  2. Click Import cURL
  3. Paste curl 'http://hostname' -H 'content-type: application/json' --data-raw '{"size":100}'
  4. Integer 100 converted to string "100"

Expected behavior

100 must be marked as an integer

Debug Info

Debug info

core

  • n8nVersion: 2.18.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 302eaf93-9af5-42d8-8578-2b32ec5bf2ad

storage

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

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 100000 executions

client

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

Generated at: 2026-04-28T11:29:22.050Z

Operating System

Ubuntu 24.04

n8n Version

2.18.4

Node.js Version

24.14.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The Import cURL function in n8n is converting integer values to strings, and a potential workaround is to manually adjust the imported JSON data to correctly represent integers.

Guidance

  • Verify that the issue is specific to the Import cURL function by comparing its behavior with manual JSON data entry in the HTTP Request node.
  • Consider using a JSON parsing or formatting node after the HTTP Request node to explicitly convert string values back to integers where necessary.
  • Review the n8n documentation for any existing options or settings that might control how the Import cURL function handles data types during import.
  • If the issue persists, check for any open issues or feature requests in the n8n community or GitHub repository related to data type handling in the Import cURL function.

Example

No specific code example is provided due to the nature of the issue being related to the n8n workflow editor's functionality rather than a code snippet.

Notes

The behavior described might be a known limitation or an intended feature of the Import cURL function in n8n version 2.18.4, and checking for updates or community discussions is recommended.

Recommendation

Apply workaround: Manually adjust the imported JSON data or use additional nodes for data type correction, as the current version's Import cURL function may not support automatic integer detection.

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

100 must be marked as an integer

#GPU setup#container setup#orchestration issue#cache issue#memory leak

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 Import cURL function in HTTP Request node doesn't handle integers in Json values. [4 comments, 4 participants]