Python Code Node (native)
Since n8n 2.0 the Code node's Python runs as native Python in a task runner (language: "pythonNative"). The old Pyodide "Python (Beta)" is gone, and with it every n8n helper it had:
_input, _json, _node, _now, _today and _jmespath all raise NameError now. Code copied
from old templates, forum posts or older docs usually breaks on this.
JavaScript first — stronger than before
Native Python gives you two variables and plain Python, and by default no imports: no
json, datetime or re. Everything n8n-specific ($('Node'), $jmespath, Luxon,
this.helpers.httpRequest, static data) exists only in JavaScript. Use Python only when the user
explicitly asks for it. Even then, first check whether an expression, Edit Fields, or a native
node (Crypto, Date & Time, HTML, XML) does the job. See n8n-code-javascript and the transform
gatekeeper in n8n-expression-syntax.
Quick start
# Run Once for All Items (default mode)
return [
{"json": {"name": it["json"]["name"], "revenue": it["json"]["revenue"]}}
for it in _items
if it["json"].get("active")
]
# Run Once for Each Item
row = _item["json"]
return {"json": {**row, "name_upper": (row.get("name") or "").upper()}}
Node config: {"language": "pythonNative", "mode": "runOnceForAllItems" | "runOnceForEachItem", "pythonCode": "..."} on n8n-nodes-base.code typeVersion 2.
The only inputs: _items and _item
| Mode |
Variable |
Shape |
| Run Once for All Items |
_items |
list of plain dicts {"json": {...}, "pairedItem": {...}} |
| Run Once for Each Item |
_item |
one plain dict {"json": {...}, "pairedItem": {...}} |
- Each variable exists only in its own mode.
_items in each-item mode (or _item in
all-items mode) raises NameError.
- Dict access only.
it["json"]["name"] or it["json"].get("name"). it.json.name raises
AttributeError: 'dict' object has no attribute 'json'.
- No other nodes. There is no
_node / $('Node') equivalent. If you need data from another
branch, bring it in with Merge first, or read it in JavaScript.
- Webhook payloads are under
["body"]: _items[0]["json"].get("body", {}).get("email").
- Binary data isn't covered here. Read and write binary in JavaScript (see n8n-binary-and-data).
- pairedItem: returning
_items / _item keeps it. When you build new dicts and downstream
uses $('Node').item, add "pairedItem": {"item": i} to each returned item. That isn't
verified on native Python yet, so test-run before relying on it.
- Missing keys: prefer
.get(key, default). row["missing"] raises KeyError.
Migration table for legacy code:
| Legacy (Pyodide) |
Native |
_input.all() |
_items |
_input.first()["json"] |
_items[0]["json"] (guard if _items) |
_input.item / _json |
_item / _item["json"] |
_node["X"] |
not available: Merge upstream, or use JS |
_now, _today |
not available: pass {{ $now.toISO() }} in via Edit Fields, or use JS |
_jmespath(data, q) |
not available: $jmespath in an expression, or a comprehension |
item.json.field |
item["json"]["field"] |
Imports: blocked by default
Every import (standard library and third-party) is checked against an allowlist before the
code runs. The default allowlist is empty, so even import json rejects the whole node:
Security violations detected
Line 1: Import of standard library module 'json' is disallowed. Allowed stdlib modules: none
- n8n Cloud: no imports at all.
- Self-hosted: the admin can allowlist modules in the task-runner config (see
n8n-self-hosting →
TASK_RUNNERS.md). Some instances therefore allow json, datetime
and re, and most don't.
- Default to import-free code. If an import would really help, confirm it first: a
one-line test node
import json + return [{"json": {"ok": True}}], or ask the user. Never
assume.
- Without imports: parse JSON strings upstream (
{{ JSON.parse($json.payload) }} in Edit Fields).
Do date math in expressions (Luxon) or JS. ISO-8601 strings still compare and sort correctly as
plain strings. Use the Crypto node for hashing.
requests, pandas and numpy are never available unless the admin built a custom runner
image. Use the HTTP Request node for HTTP.
Sandbox limits (these fail even without imports)
| You write |
What happens |
Use instead |
eval, exec, compile, open, input, type, getattr, setattr, hasattr, vars, dir, globals, locals, object, memoryview, breakpoint |
NameError: name 'type' is not defined (runtime) |
isinstance(x, dict); key in d / d.get(key) |
class Foo: ... |
__build_class__ not found (runtime) |
dicts + functions |
x.__class__, "{0.__class__}".format(x), __import__("json") |
Security violations detected (whole node rejected before running) |
— |
global counter inside a function |
NameError: name 'counter' is not defined, because your code runs inside a wrapper function |
nonlocal counter |
Everything else in plain Python works (verified): comprehensions, generators, lambdas, closures,
recursion, try/except, f-strings / .format() / %, sorted/min/max/sum/any/all/
enumerate/zip/round, sets, isinstance, print() (output goes to the browser console).
Return shapes (verified)
Observed on n8n 2.38.5. The auto-wrapping and passthrough behaviours below are undocumented and could
change in a later release. Re-check with a test run after upgrading n8n.
Run Once for All Items
| Return |
Result |
[{"json": {...}}, ...] |
canonical, N items |
[{...}, ...] (plain dicts) |
auto-wrapped under json, N items |
{"json": {...}} or a single plain dict |
1 item |
_items (mutated in place) |
passthrough with your changes |
None / no return |
error Cannot read properties of null (reading 'json') |
Run Once for Each Item
| Return |
Result |
{"json": {...}}, a plain dict, or _item |
1 item |
None |
the item is dropped (a built-in filter) |
| a list |
error A 'json' property isn't a dictionary [item 0] |
Value conversion on output: tuple becomes a list, set becomes the string "{1, 2}",
and a datetime becomes str(dt) ("2026-09-16 10:18:00.025792", not ISO). Convert explicitly
(sorted(s), dt.isoformat()).
Prefer the explicit [{"json": ...}] in all-items mode and {"json": ...} in each-item mode.
The auto-wrapping works, but the explicit shape makes the intent obvious to the next reader.
Errors and onError
A plain raise ValueError("bad row") fails the node with that message. When the node has an
onError continue mode, the three failure kinds behave differently (verified):
| Failure |
continueErrorOutput |
continueRegularOutput |
Runtime exception (raise, KeyError, NameError, denied builtin) |
{"error": "<message>"} on the error output (main[1]) ✅ |
{"error": "<message>"} on the main output |
Static rejection (Security violations detected: import, dunder) |
node marked failed, but the input items, unchanged, go out the success output; main[1] stays empty |
input items, unchanged, on the main output |
Bad return shape (list in each-item mode, None in all-items mode) |
same: unchanged input on the success output |
same |
The last two are silent-data traps: downstream nodes receive unprocessed input as if the code had
run, and the execution still shows success. No error branch catches them. Prevent them (no
imports unless confirmed, correct return shape) and confirm with a real test run, checking the
Code node's status and output (see n8n-error-handling).
Other messages:
Python runner unavailable: Python 3 is missing from this system: the self-hosted instance has
no Python task runner (the stock image ships none). It's an infrastructure problem, not a code
problem. See n8n-self-hosting → TASK_RUNNERS.md.
validate_node / validate_workflow catch a few Python mistakes (import requests, missing
return, return None). They do not catch _input/_json, dot access, blocked stdlib
imports, dunder access or classes. A test execution is the only reliable check.
Performance
Each Python Code node costs roughly 0.4 s (about 1 s when the runner is cold), noticeably more
than a JS Code node or an expression. Process lists in Run Once for All Items mode rather than
per item, and don't chain several small Python nodes where one would do.
Checklist
Reference
- COMMON_PATTERNS.md: 12 import-free patterns, each verified on a live
n8n instance (filter, aggregate, group, dedupe, top N, flatten, validate, drop items, text
report, safe nested access, running totals, ISO timestamps).
Related skills
- n8n-code-javascript: the default for Code nodes, with all n8n helpers.
- n8n-expression-syntax:
$jmespath, Luxon and the transform gatekeeper, often a better fit than any Code node.
- n8n-code-tool: Python in the AI-agent Custom Code Tool (
_query, returns a string).
- n8n-error-handling: wiring error outputs; the passthrough trap above.
- n8n-self-hosting: enabling the Python task runner and allowlisting modules.
1---2name: n8n-code-python-23description: Write Python in n8n Code nodes (native Python, `language` pythonNative, n8n 2.x). Use when the user explicitly wants Python in a Code node, when migrating old Pyodide/"Python (Beta)" code that used _input/_json/_node/_now, or when a Python Code node fails with NameError, "Security violations detected", "Import of standard library module … is disallowed", "__build_class__ not found", "A 'json' property isn't a dictionary", or "Python runner unavailable". Covers the only two variables (_items/_item), dict-only access, imports blocked by default, the sandbox's denied builtins, accepted return shapes, and how errors interact with onError. JavaScript is the default for Code nodes — native Python has no n8n helpers and, by default, no imports. EXCEPTION — for Python in the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode), use the n8n-code-tool skill instead (input is _query, return must be a string).4metadata:5 source: https://skillmd.com/skills/agents-store/n8n-code-python-26---78# Python Code Node (native)910Since n8n 2.0 the Code node's Python runs as **native Python in a task runner** (`language:11"pythonNative"`). The old Pyodide "Python (Beta)" is gone, and with it every n8n helper it had:12`_input`, `_json`, `_node`, `_now`, `_today` and `_jmespath` all raise `NameError` now. Code copied13from old templates, forum posts or older docs usually breaks on this.1415---1617## JavaScript first — stronger than before1819Native Python gives you two variables and plain Python, and **by default no imports**: no20`json`, `datetime` or `re`. Everything n8n-specific (`$('Node')`, `$jmespath`, Luxon,21`this.helpers.httpRequest`, static data) exists only in JavaScript. Use Python only when the user22explicitly asks for it. Even then, first check whether an expression, Edit Fields, or a native23node (Crypto, Date & Time, HTML, XML) does the job. See **n8n-code-javascript** and the transform24gatekeeper in **n8n-expression-syntax**.2526---2728## Quick start2930```python31# Run Once for All Items (default mode)32return [33 {"json": {"name": it["json"]["name"], "revenue": it["json"]["revenue"]}}34 for it in _items35 if it["json"].get("active")36]37```3839```python40# Run Once for Each Item41row = _item["json"]42return {"json": {**row, "name_upper": (row.get("name") or "").upper()}}43```4445Node config: `{"language": "pythonNative", "mode": "runOnceForAllItems" | "runOnceForEachItem",46"pythonCode": "..."}` on `n8n-nodes-base.code` typeVersion 2.4748---4950## The only inputs: `_items` and `_item`5152| Mode | Variable | Shape |53|---|---|---|54| Run Once for All Items | `_items` | `list` of plain dicts `{"json": {...}, "pairedItem": {...}}` |55| Run Once for Each Item | `_item` | one plain dict `{"json": {...}, "pairedItem": {...}}` |5657- Each variable exists **only in its own mode**. `_items` in each-item mode (or `_item` in58 all-items mode) raises `NameError`.59- **Dict access only.** `it["json"]["name"]` or `it["json"].get("name")`. `it.json.name` raises60 `AttributeError: 'dict' object has no attribute 'json'`.61- **No other nodes.** There is no `_node` / `$('Node')` equivalent. If you need data from another62 branch, bring it in with Merge first, or read it in JavaScript.63- **Webhook payloads** are under `["body"]`: `_items[0]["json"].get("body", {}).get("email")`.64- **Binary data** isn't covered here. Read and write binary in JavaScript (see **n8n-binary-and-data**).65- **pairedItem:** returning `_items` / `_item` keeps it. When you build new dicts and downstream66 uses `$('Node').item`, add `"pairedItem": {"item": i}` to each returned item. That isn't67 verified on native Python yet, so test-run before relying on it.68- Missing keys: prefer `.get(key, default)`. `row["missing"]` raises `KeyError`.6970Migration table for legacy code:7172| Legacy (Pyodide) | Native |73|---|---|74| `_input.all()` | `_items` |75| `_input.first()["json"]` | `_items[0]["json"]` (guard `if _items`) |76| `_input.item` / `_json` | `_item` / `_item["json"]` |77| `_node["X"]` | not available: Merge upstream, or use JS |78| `_now`, `_today` | not available: pass `{{ $now.toISO() }}` in via Edit Fields, or use JS |79| `_jmespath(data, q)` | not available: `$jmespath` in an expression, or a comprehension |80| `item.json.field` | `item["json"]["field"]` |8182---8384## Imports: blocked by default8586Every `import` (standard library and third-party) is checked against an allowlist **before the87code runs**. The default allowlist is empty, so even `import json` rejects the whole node:8889```90Security violations detected91Line 1: Import of standard library module 'json' is disallowed. Allowed stdlib modules: none92```9394- **n8n Cloud:** no imports at all.95- **Self-hosted:** the admin can allowlist modules in the task-runner config (see96 **n8n-self-hosting** → `TASK_RUNNERS.md`). Some instances therefore allow `json`, `datetime`97 and `re`, and most don't.98- **Default to import-free code.** If an import would really help, confirm it first: a99 one-line test node `import json` + `return [{"json": {"ok": True}}]`, or ask the user. Never100 assume.101- Without imports: parse JSON strings upstream (`{{ JSON.parse($json.payload) }}` in Edit Fields).102 Do date math in expressions (Luxon) or JS. ISO-8601 strings still compare and sort correctly as103 plain strings. Use the Crypto node for hashing.104- `requests`, `pandas` and `numpy` are never available unless the admin built a custom runner105 image. Use the HTTP Request node for HTTP.106107---108109## Sandbox limits (these fail even without imports)110111| You write | What happens | Use instead |112|---|---|---|113| `eval`, `exec`, `compile`, `open`, `input`, `type`, `getattr`, `setattr`, `hasattr`, `vars`, `dir`, `globals`, `locals`, `object`, `memoryview`, `breakpoint` | `NameError: name 'type' is not defined` (runtime) | `isinstance(x, dict)`; `key in d` / `d.get(key)` |114| `class Foo: ...` | `__build_class__ not found` (runtime) | dicts + functions |115| `x.__class__`, `"{0.__class__}".format(x)`, `__import__("json")` | `Security violations detected` (whole node rejected before running) | — |116| `global counter` inside a function | `NameError: name 'counter' is not defined`, because your code runs inside a wrapper function | `nonlocal counter` |117118Everything else in plain Python works (verified): comprehensions, generators, lambdas, closures,119recursion, `try`/`except`, f-strings / `.format()` / `%`, `sorted`/`min`/`max`/`sum`/`any`/`all`/120`enumerate`/`zip`/`round`, sets, `isinstance`, `print()` (output goes to the browser console).121122---123124## Return shapes (verified)125126Observed on n8n 2.38.5. The auto-wrapping and passthrough behaviours below are undocumented and could127change in a later release. Re-check with a test run after upgrading n8n.128129**Run Once for All Items**130131| Return | Result |132|---|---|133| `[{"json": {...}}, ...]` | canonical, N items |134| `[{...}, ...]` (plain dicts) | auto-wrapped under `json`, N items |135| `{"json": {...}}` or a single plain dict | 1 item |136| `_items` (mutated in place) | passthrough with your changes |137| `None` / no `return` | error `Cannot read properties of null (reading 'json')` |138139**Run Once for Each Item**140141| Return | Result |142|---|---|143| `{"json": {...}}`, a plain dict, or `_item` | 1 item |144| `None` | the item is **dropped** (a built-in filter) |145| a **list** | error `A 'json' property isn't a dictionary [item 0]` |146147**Value conversion on output:** `tuple` becomes a list, `set` becomes the *string* `"{1, 2}"`,148and a `datetime` becomes `str(dt)` (`"2026-09-16 10:18:00.025792"`, not ISO). Convert explicitly149(`sorted(s)`, `dt.isoformat()`).150151Prefer the explicit `[{"json": ...}]` in all-items mode and `{"json": ...}` in each-item mode.152The auto-wrapping works, but the explicit shape makes the intent obvious to the next reader.153154---155156## Errors and `onError`157158A plain `raise ValueError("bad row")` fails the node with that message. When the node has an159`onError` continue mode, the three failure kinds behave **differently** (verified):160161| Failure | `continueErrorOutput` | `continueRegularOutput` |162|---|---|---|163| Runtime exception (`raise`, `KeyError`, `NameError`, denied builtin) | `{"error": "<message>"}` on the error output (`main[1]`) ✅ | `{"error": "<message>"}` on the main output |164| Static rejection (`Security violations detected`: import, dunder) | node marked failed, but the **input items, unchanged, go out the success output**; `main[1]` stays empty | input items, unchanged, on the main output |165| Bad return shape (list in each-item mode, `None` in all-items mode) | same: **unchanged input on the success output** | same |166167The last two are silent-data traps: downstream nodes receive unprocessed input as if the code had168run, and the execution still shows success. No error branch catches them. Prevent them (no169imports unless confirmed, correct return shape) and confirm with a real test run, checking the170Code node's status and output (see **n8n-error-handling**).171172Other messages:173174- `Python runner unavailable: Python 3 is missing from this system`: the self-hosted instance has175 no Python task runner (the stock image ships none). It's an infrastructure problem, not a code176 problem. See **n8n-self-hosting** → `TASK_RUNNERS.md`.177- `validate_node` / `validate_workflow` catch a few Python mistakes (`import requests`, missing178 `return`, `return None`). They do **not** catch `_input`/`_json`, dot access, blocked stdlib179 imports, dunder access or classes. A test execution is the only reliable check.180181---182183## Performance184185Each Python Code node costs roughly 0.4 s (about 1 s when the runner is cold), noticeably more186than a JS Code node or an expression. Process lists in **Run Once for All Items** mode rather than187per item, and don't chain several small Python nodes where one would do.188189---190191## Checklist192193- [ ] The user actually asked for Python. Otherwise JS, an expression, or a native node.194- [ ] Mode matches the variable: `_items` (all items) / `_item` (each item).195- [ ] Only dict access. No `_input`, `_json`, `_node`, `_now` or `_jmespath`.196- [ ] No `import` unless confirmed allowlisted on *this* instance.197- [ ] No classes, `type()`, `getattr`/`hasattr` or dunders. `nonlocal` instead of `global`.198- [ ] Return shape fits the mode. Sets and datetimes converted explicitly.199- [ ] Ran a real test execution and inspected the output items (validation alone won't catch the traps above).200201---202203## Reference204205- **[COMMON_PATTERNS.md](COMMON_PATTERNS.md)**: 12 import-free patterns, each verified on a live206 n8n instance (filter, aggregate, group, dedupe, top N, flatten, validate, drop items, text207 report, safe nested access, running totals, ISO timestamps).208209## Related skills210211- **n8n-code-javascript**: the default for Code nodes, with all n8n helpers.212- **n8n-expression-syntax**: `$jmespath`, Luxon and the transform gatekeeper, often a better fit than any Code node.213- **n8n-code-tool**: Python in the AI-agent Custom Code Tool (`_query`, returns a string).214- **n8n-error-handling**: wiring error outputs; the passthrough trap above.215- **n8n-self-hosting**: enabling the Python task runner and allowlisting modules.