Code Node (& Function Node)

The Code Node runs synchronous JavaScript in a secure code sandbox. No async, no network, no modules.

Written By pvdyck

Last updated 1 day ago

⚠️ Limitations — Works with known restrictions, see details below

On indie.money, the Code node runs in a secure code sandbox instead of Node.js:

Feature	Status
JavaScript (sync)	Supported
All n8n variables (`$input`, `$json`, `$node`, `$workflow`, etc.)	Supported
`$now`, `$today`, `DateTime` (Luxon-like)	Supported
`$('NodeName')`, `$node['Name']`	Supported
Python	Not supported — JavaScript only
async/await	Not supported — synchronous execution only
fetch / HTTP	Not supported — use HTTP Request node instead
this.helpers	Not supported — n8n helper methods are not available in the sandbox
require / import	Not supported — no external modules
console.log	Not supported — use `return` to output data
process.env	Not supported — use `$env` or `$vars` for environment variables
File system	Not supported — no fs access
`$getWorkflowStaticData`	Partial — works within a single execution but not persisted between runs
`$jmespath`	Not supported — Use Array methods (filter, map, find) instead
`$fromAI`	Not supported
`$evaluateExpression`	Not supported — Expressions must be resolved before the Code node
DateTime.fromFormat()	Not supported — Use `DateTime.fromISO()` or `new Date(string)`
DateTime.fromRFC2822()	Not supported
Interval	Not supported
Duration	Not supported — Use `$now.plus({days: 1})` for date arithmetic
`$self`	Partial — Returns empty object. Not populated until after Code node executes

Limits:

30-second CPU time — active processing only, not wall-clock. Time spent waiting on network responses (HTTP Request, LLM calls) does not count toward this limit.
5-minute wall-clock timeout — total elapsed time including I/O wait. An agent can spend up to 5 minutes total but no more than 30 seconds of that running CPU-bound code.

This integration works on indie.money with known limitations. See the details above for specifics.