n8n - 💡(How to fix) Fix Import cURL fails in HTTP Request node

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…
RAW_BUFFERClick to expand / collapse

Bug Description

Clicking the import button not doing anything.

To Reproduce

Open a workflow Add an HTTP Request node Open Import cURL Paste a valid cURL command Click Import

Expected behavior

The cURL command should be imported successfully and the HTTP Request node fields should be filled automatically.

Debug Info

Debug

Operating System

Mac

n8n Version

Free trial

Node.js Version

24.0.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The issue might be resolved by checking the cURL command for validity and ensuring that the Import button is functioning correctly in the n8n workflow editor.

Guidance

  • Verify that the pasted cURL command is valid and properly formatted to ensure it can be correctly imported into the HTTP Request node.
  • Check the n8n workflow editor for any error messages or warnings after clicking the Import button to identify potential issues.
  • Ensure that the HTTP Request node is properly configured and compatible with the imported cURL command.
  • Test the import process with a simple cURL command to isolate the issue and determine if it's specific to the command being imported.

Notes

The provided information does not include specific details about the cURL command being imported or any error messages that may be occurring, which could be crucial in diagnosing the issue.

Recommendation

Apply workaround: Test the import process with a simple cURL command to isolate the issue, as the problem might be specific to the command being imported or a configuration issue within the n8n workflow editor.

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

The cURL command should be imported successfully and the HTTP Request node fields should be filled automatically.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING