HTTP Request Node import Curl Command not working

mardijkers · March 9, 2025, 8:18am

Issue: Unable to Import cURL – Import Button Not Working

Describe the Problem

I’m trying to import a cURL command into n8n, but it’s not working as expected. When I copy and paste the cURL command and press the Import button, nothing happens—no response, and no workflow is imported.

What is the Error Message (if any)?

There is no visible error message, but the import process does not work.

Steps to Reproduce

Open n8n Editor UI
Click on the Import button
Paste a valid cURL command
Click Import
Nothing happens, and no workflow is generated

Expected Behavior

n8n should parse the cURL command and convert it into an HTTP Request node within my workflow.

Information on My n8n Setup

n8n version: 1.81.4
Database: PostgreSQL
n8n EXECUTIONS_PROCESS setting: default
Running n8n via: npm
Operating System: Ubuntu 22.04

Example cURL Command

curl --request POST \
  --url https://api.cal.com/v2/bookings \
  --header 'Content-Type: application/json' \
  --header 'cal-api-version: <cal-api-version>' \
  --data '{
  "start": "2024-08-13T09:00:00Z",
  "lengthInMinutes": 30,
  "eventTypeId": 123,
  "attendee": {
    "name": "John Doe",
    "email": "[email protected]",
    "timeZone": "America/New_York",
    "phoneNumber": "+919876543210",
    "language": "it"
  },
  "guests": [
    "[email protected]",
    "[email protected]"
  ],
  "meetingUrl": "https://example.com/meeting",
  "location": "https://example.com/meeting",
  "metadata": {
    "key": "value"
  },
  "bookingFieldsResponses": {
    "customField": "customValue"
  }

Has anyone else encountered this issue? Any suggestions on how to fix or debug it?

Alex_Huang · March 9, 2025, 8:42am

@mardijkers could you drop the cURL command here?

mardijkers · March 9, 2025, 8:50am

I edited my question to include a cURL sample, but I’ve tried other cURL commands, and the issue still persists

Michael_Flanagan · March 9, 2025, 2:52pm

I am seeing the same issue this morning.

Brandon_Elliott · March 9, 2025, 4:33pm

Thank you for this thread. I was having the same problem with curl import (nothing). I temporarily pulled the nightly and it’s working again.

paryupaa · March 10, 2025, 2:43pm

Hey, same issue here. It’s like if the import button was disabled…

hermanndelcampo · March 10, 2025, 2:50pm

mardijkers:

curl --request POST \
  --url https://api.cal.com/v2/bookings \
  --header 'Content-Type: application/json' \
  --header 'cal-api-version: <cal-api-version>' \
  --data '{
  "start": "2024-08-13T09:00:00Z",
  "lengthInMinutes": 30,
  "eventTypeId": 123,
  "attendee": {
    "name": "John Doe",
    "email": "[email protected]",
    "timeZone": "America/New_York",
    "phoneNumber": "+919876543210",
    "language": "it"
  },
  "guests": [
    "[email protected]",
    "[email protected]"
  ],
  "meetingUrl": "https://example.com/meeting",
  "location": "https://example.com/meeting",
  "metadata": {
    "key": "value"
  },
  "bookingFieldsResponses": {
    "customField": "customValue"
  }

The error you’re encountering likely stems from an issue in the JSON payload. In your cURL command, the JSON provided after the --data flag is missing its final closing curly brace and the closing quote. This makes the JSON invalid, which in turn causes n8n to reject the format.

Here is the corrected code.

Then it works

curl --request POST \
  --url https://api.cal.com/v2/bookings \
  --header 'Content-Type: application/json' \
  --header 'cal-api-version: <cal-api-version>' \
  --data '{
  "start": "2024-08-13T09:00:00Z",
  "lengthInMinutes": 30,
  "eventTypeId": 123,
  "attendee": {
    "name": "John Doe",
    "email": "[email protected]",
    "timeZone": "America/New_York",
    "phoneNumber": "+919876543210",
    "language": "it"
  },
  "guests": [
    "[email protected]",
    "[email protected]"
  ],
  "meetingUrl": "https://example.com/meeting",
  "location": "https://example.com/meeting",
  "metadata": {
    "key": "value"
  },
  "bookingFieldsResponses": {
    "customField": "customValue"
  }
}'

hermanndelcampo · March 10, 2025, 2:52pm

My proof, that it works

Guy_Pavlov · March 10, 2025, 10:36pm

The modified prompt didn’t work for me.
You might be using a different version of n8n from the one causing the problem

Gaurav_Kumar_Singh · March 11, 2025, 10:02am

I am giving this curl

curl -X POST https://api.firecrawl.dev/v1/extract
-H ‘Content-Type: application/json’
-H ‘Authorization: Bearer YOUR_API_KEY’
-d ‘{
“urls”: [
“https://firecrawl.dev/”,
“https://docs.firecrawl.dev/”,
“The YC Startup Directory | Y Combinator”
],
“prompt”: “Extract the company mission, whether it supports SSO, whether it is open source, and whether it is in Y Combinator from the page.”,
“schema”: {
“type”: “object”,
“properties”: {
“company_mission”: {
“type”: “string”
},
“supports_sso”: {
“type”: “boolean”
},
“is_open_source”: {
“type”: “boolean”
},
“is_in_yc”: {
“type”: “boolean”
}
},
“required”: [
“company_mission”,
“supports_sso”,
“is_open_source”,
“is_in_yc”
]
}
}’

getting same issue import is not working can any one sugget the solution Thankyou

Adrian_Joss · March 11, 2025, 12:47pm

Same Issue for me, I think it may be a version issue, I am on Version 1.81.4 it when you click the Import button it does nothing at all, not even an error message, it’s behaviour is like the import button is inactive.

jake88 · March 11, 2025, 1:31pm

Same problem here. Exactly as described by previous users. Button does not respons.

capoyeti · March 11, 2025, 6:13pm

Same problem - same description.

Hanson_Cheng · March 11, 2025, 6:21pm

same issue. there is a bug. just stopped working

Ed_P · March 11, 2025, 11:36pm

I second this. Same problem with cURL import in the Community Self-hosted instance ver 1.81.4

Here’s what I see in the browser Dev Tools. The same when trying to import empty cURL or anything entered:

hermanndelcampo · March 12, 2025, 6:28pm

For testing purpse I used latest community edition and tested it.

In Community edition the import is not working.
In Cloud Version it is working.

nicktomic · March 13, 2025, 10:12am

It’s not working for me either.

Anthony · March 13, 2025, 12:03pm

I can confirm cURL import is broken in self-hosted version 1.81.4

Looking in Chrome Dev Tools console, it looks like tree-sitter.wasm is not found and throws 404 error

muffingman · March 13, 2025, 10:17pm

hey! thanks for pointing this out, I just updated to the latest image on docker for the community edition and it is now cURL importing just fine.

Gaurav_Kumar_Singh · March 14, 2025, 4:01am

Hey I am using cloud version I am still facing the same issue that import curl is not working can anyone any solution for this please.