cURL to n8n Converter

A cURL to n8n converter turns a curl command from API docs into an n8n HTTP Request node. Paste one or more commands and this free tool maps the method, URL, query, headers, JSON or form body and basic auth to node parameters, explains every field and outputs JSON you paste straight onto the canvas. API keys can be moved into n8n credentials.

Free, no signup. Runs entirely in your browser; files and text are not uploaded.

How to use the cURL to n8n Converter

  1. Paste one or more cURL commands into the input, or load a sample.
  2. Choose how to handle API keys: move them to an n8n credential, use placeholders or keep them.
  3. Check the field-by-field summary and any notes about ignored options.
  4. Click Copy n8n node, then click the n8n canvas and press Ctrl+V (Cmd+V).
  5. If the node uses a credential, create it in n8n and select it in the node.

Features

  • Parses -X, -H, -d, --data-raw, --data-binary, --data-urlencode, --json, -F, -u, -G, -k and -m
  • Handles backslash line continuations and single, double and $'…' quotes
  • Outputs an HTTP Request node (typeVersion 4.2) in n8n’s paste format
  • Detects Authorization, API-key and token headers and query parameters
  • Moves one secret into a Basic, Header or Query Auth credential, or replaces it with a placeholder
  • Converts several commands at once and explains each mapped field

Frequently asked questions

Doesn’t n8n already have Import cURL?

Yes, the HTTP Request node has an Import cURL button. This tool adds batch conversion, a table explaining each mapped field, notes on ignored options and secret handling. n8n’s import puts -u credentials into an Authorization header; here you can move them into a credential instead.

How do I paste the result into n8n?

Click Copy n8n node, open your workflow, click an empty spot on the canvas and press Ctrl+V (Cmd+V on Mac). The JSON uses the {"nodes": [...], "connections": {}} shape that n8n accepts on paste.

Why move API keys into credentials?

Values typed into node parameters are saved in the workflow and included when you copy, export or share it. n8n credentials are stored separately, and exported workflows only contain the credential name and ID.

Is my cURL command sent to a server?

No. Parsing and conversion run entirely in your browser, so commands, tokens and passwords never leave your device.

Related tools

  • Cron Expression Generator – Build or explain cron expressions, see the next 10 runs in any time zone and copy an n8n Schedule Trigger
  • JSON Formatter – Beautify, minify and validate JSON with error line numbers, key sorting and auto-fix
  • URL Encoder – Percent-encode or decode URLs and query strings, with form (+) and component modes
  • Base64 Encoder – Encode text or files to Base64 and decode it back, with UTF-8 and URL-safe support
  • JWT Decoder – Decode JWT header, payload and claims with expiry status – signatures are not verified

Built and reviewed by Naqash Thaheem, Technical Project Manager. Last reviewed 2026-09-25.