Encode and decode Base64, base64url and MIME with UTF-8-safe text for Arabic and emoji
cURL to n8n HTTP Request Node
Paste a cURL command to get an n8n HTTP Request node JSON: method, URL, query, headers and body (JSON, form or multipart), with secret redaction and timeout and retry settings.
Workspace
Node
How the result is calculated
The command is tokenised with shell quoting rules ('…', "…", \ escapes and line continuation). Parsed options: -X/--request, -H, -d/--data*, --data-urlencode, -F, -u, -G, -I, --json, --url, -A/-e/-b; value-less flags (-L -k -s --compressed…) are ignored. The default method is GET, and POST when a body exists. Body type: JSON when Content-Type contains json or the text is valid JSON, otherwise urlencoded form, multipart with -F, or raw with another Content-Type. The URL query is split into parameters. Authorization, x-api-key, Cookie and the -u password are redacted.
Limits:
The node field names (typeVersion 4.2) come from my knowledge of n8n’s structure and were not verified against every version: try the node in n8n and adjust if needed.
$'…', shell variables and --data @file are not supported. It does not create the credential: a Basic Auth node needs it attached manually. Pagination and OAuth2 are not included.FAQ
Are my keys stored?
No; everything stays in your browser and sensitive values are redacted by default.
Why is the body JSON?
Because Content-Type contains json or the text is valid JSON.
