Generated banner for N8n Code Python
Generated logo for N8n Code Python

N8n Code Python

Romuald CzlonkowskiCommunityCreated by Romuald Czlonkowski

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found

From the author

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).
— the description by Romuald Czlonkowski

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides essential guidelines for using the native Python runner in n8n 2.x Code nodes. Unlike the legacy Pyodide implementation, native Python runs in a restricted task runner environment without access to n8n-specific helpers like _input, _json, or _node. Users must adhere to strict sandbox limitations, including blocked imports by default, restricted built-in functions, and specific return shape requirements. This documentation helps developers migrate legacy code, troubleshoot common runtime errors, and optimize performance for Python-based data transformations within n8n workflows.

What it does

  • Explains the use of _items and _item variables for data access in different execution modes.
  • Details the security sandbox, including blocked imports and restricted built-in functions.
  • Provides migration patterns for transitioning from legacy Pyodide code to native Python.
  • Defines valid return shapes for both 'Run Once for All Items' and 'Run Once for Each Item' modes.
  • Outlines performance considerations and error handling behaviors for node failures.
  • Offers a checklist for verifying Python code before deployment.

When to use it

  • When a workflow explicitly requires Python logic that cannot be achieved via standard n8n nodes or JavaScript.
  • When migrating legacy n8n workflows that previously relied on Pyodide-based Python nodes.
  • When troubleshooting NameError or Security violation errors in existing Python Code nodes.
  • When you need to perform complex data manipulations that benefit from Python's native syntax.

Advantages

  • Enables the use of native Python syntax, including comprehensions, generators, and lambdas.
  • Provides clear guidance on avoiding silent data traps during error handling.
  • Clarifies the distinction between native Python and JavaScript-based n8n helpers.
  • Helps optimize workflow performance by recommending efficient execution modes.

Usage examples

“How do I filter items in a native Python Code node?”
Use 'Run Once for All Items' mode and return a list comprehension: return [it for it in _items if it['json'].get('active')].
“Why am I getting a NameError when using _input in my Python node?”
The _input helper is not available in native Python. Replace it with _items for 'Run Once for All Items' mode or _item for 'Run Once for Each Item' mode.
“Can I import the json module in my Python Code node?”
Imports are blocked by default. You must check if your n8n instance administrator has allowlisted the module in the task-runner configuration.
“How do I return data from a Python Code node?”
In 'Run Once for All Items' mode, return a list of dictionaries, e.g., [{'json': {'key': 'value'}}]. In 'Run Once for Each Item' mode, return a single dictionary.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/czlonkowski/n8n-code-python/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip n8n-code-python.zip -d .agents/skills

Documentation by Romuald Czlonkowski

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

ModeVariableShape
Run Once for All Items_itemslist of plain dicts {"json": {...}, "pairedItem": {...}}
Run Once for Each Item_itemone 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, _todaynot 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.fielditem["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 with the Date & Time node or Luxon in an expression. 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 writeWhat happensUse instead
eval, exec, compile, open, input, type, getattr, setattr, hasattr, vars, dir, globals, locals, object, memoryview, breakpointNameError: 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 functionNameError: name 'counter' is not defined, because your code runs inside a wrapper functionnonlocal 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

ReturnResult
[{"json": {...}}, ...]canonical, N items
[{...}, ...] (plain dicts)auto-wrapped under json, N items
{"json": {...}} or a single plain dict1 item
_items (mutated in place)passthrough with your changes
None / no returnerror Cannot read properties of null (reading 'json')

Run Once for Each Item

ReturnResult
{"json": {...}}, a plain dict, or _item1 item
Nonethe item is dropped (a built-in filter)
a listerror 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):

FailurecontinueErrorOutputcontinueRegularOutput
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 emptyinput 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 outputsame

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

  • [ ] The user actually asked for Python. Otherwise JS, an expression, or a native node.

  • [ ] Mode matches the variable: _items (all items) / _item (each item).

  • [ ] Only dict access. No _input, _json, _node, _now or _jmespath.

  • [ ] No import unless confirmed allowlisted on this instance.

  • [ ] No classes, type(), getattr/hasattr or dunders. nonlocal instead of global.

  • [ ] Return shape fits the mode. Sets and datetimes converted explicitly.

  • [ ] Ran a real test execution and inspected the output items (validation alone won't catch the traps above).


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).

  • 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.

Files

README.md

n8n Code Python Skill

Guidance for writing native Python in n8n Code nodes (language: "pythonNative", n8n 2.x).


Why this skill exists

n8n 2.0 removed the Pyodide-based "Python (Beta)" and replaced it with native Python running in a task runner. A large share of the Python n8n code in circulation (templates, forum answers, older docs, model training data) targets the old runtime and fails on the new one:

  • _input, _json, _node, _now, _today, _jmespath → NameError (only _items / _item exist)

  • item.json.field → AttributeError (dict access only)

  • import json → Security violations detected (every import is blocked unless the instance allowlists it; n8n Cloud allows none)

  • class Foo: → __build_class__ not found; type(), getattr(), hasattr() → NameError

The skill teaches the runtime as it actually behaves. Every rule and pattern was verified by execution on n8n 2.38.5, and the skill keeps pushing agents toward JavaScript, expressions, and native nodes whenever the user hasn't explicitly asked for Python.


Skill activation

  • The user explicitly wants a Python Code node

  • Migrating legacy Pyodide Python (_input.all(), _json, _node[...])

  • A Python Code node fails with NameError, Security violations detected, Import of standard library module … is disallowed, A 'json' property isn't a dictionary, or Python runner unavailable

Not for the AI-agent Custom Code Tool (toolCode) — that's n8n-code-tool.

Example queries:

  • "Write a Python Code node that groups these items by country."

  • "My Python Code node says name '_input' is not defined."

  • "Why can't I import json in the Python Code node?"


File structure

SKILL.md

JavaScript-first rule; _items / _item and dict-only access; legacy→native migration table; imports blocked by default (Cloud vs self-hosted allowlist); sandbox limits (denied builtins, no classes, no dunders, nonlocal instead of global); verified return shapes per mode and output value conversion; how runtime vs static vs return-shape errors behave with onError; performance; checklist.

COMMON_PATTERNS.md

12 import-free patterns, each run verbatim on a live instance with the observed output: filter and reshape, totals, group by, dedupe, top N, flatten nested arrays, validate and flag, drop items in each-item mode, text report, safe nested access, running totals with nonlocal, ISO timestamps without datetime.


  • n8n-code-javascript — the default for Code nodes

  • n8n-expression-syntax — $jmespath, Luxon, and the transform gatekeeper

  • n8n-code-tool — Python in the AI-agent Custom Code Tool

  • n8n-error-handling — error outputs and the continueRegularOutput passthrough trap

  • n8n-self-hosting — enabling the Python task runner (TASK_RUNNERS.md)


Version

Version: 2.0.0 — rewritten for native Python (n8n 2.x); replaces the Pyodide-era 1.x content (STANDARD_LIBRARY.md, DATA_ACCESS.md and ERROR_PATTERNS.md were removed because they described a runtime that no longer exists). Compatibility: n8n ≥ 2.0 Code node, language: "pythonNative".


Credits

Part of the n8n-skills project.

Conceived by Romuald Członkowski

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python, Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Romuald Czlonkowski
Publisher
Romuald Czlonkowski (Community)
Source
czlonkowski/n8n-skills · skills/n8n-code-python · commit e037563
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Romuald Czlonkowski.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download n8n-code-python.zip