n8n Code node compatibility check
Paste a Pipedream code step, Node.js or Python. You get each line the n8n Code node will reject, rated for n8n Cloud and for self-hosted n8n.
How the check works
Two verdicts per line
Each finding is rated twice: for n8n Cloud and for self-hosted n8n. A step can be fine on your own server and blocked on Cloud, mostly because of npm imports.
Rules come from real failures
We converted 92 public Pipedream workflows and ran them in n8n 2.44.5. The first errors were disallowed modules (npm and crypto), missing globals such as fetch and Python steps without a runner. Every one of those is a rule here.
Globals the Code node lacks
In our n8n 2.44.5 probe fetch, URL, URLSearchParams, AbortController, structuredClone, Blob and process were undefined. fetch() appeared in 31 of the 92 workflows.
Pipedream-only calls
$.flow.rerun, $.flow.trigger, $.flow.suspend, $.send.*, data stores, /tmp files and *.m.pipedream.net URLs. Each finding names the n8n node or setting to use instead.
Cloud vs self-hosted
On n8n Cloud the Code node loads only crypto and moment. Self-hosted n8n can allow more in the task runner. Details: n8n Cloud vs self-hosted and npm packages in n8n.
Nothing leaves the tab
The check runs in this browser tab. The code you paste is not sent to our server. For a whole export, use the converter.