[New Node] Declaw — run untrusted & AI-generated code safely in n8n (Firecracker microVM sandboxes)

Hey everyone :waving_hand:

Just published n8n-nodes-declaw as a verified community node — which means it installs directly in n8n Cloud (no self-hosting required), as well as on self-hosted instances. It lets your workflows (and AI agents) execute arbitrary code in isolated Firecracker microVM sandboxes, so AI-generated or untrusted code never touches your n8n host.

Install (Cloud or self-hosted): Settings → Community Nodes → Install → n8n-nodes-declaw

It’s a single Declaw node — usable as a normal workflow node and as an AI Agent tool — organized into resources:

  • Code Interpreter — one-shot secure Python/JS execution. Auto-manages the sandbox lifecycle (spins one up, runs your code, tears it down). Supports env vars, input/output files, a network egress allowlist, PII protection (alert/block/redact), and prompt-injection defense.

  • Sandbox — full lifecycle control: create / get / pause / resume / kill / set timeout.

  • Command / File / Snapshot — run commands, read/write/list files, and manage snapshots in a running sandbox.

Typical use cases:

  • Give an AI Agent a real code interpreter without giving it your server

  • Run user-submitted or LLM-generated scripts inside a workflow

  • Spin up ephemeral environments for data transforms, scraping, or testing

Auth is just a Declaw API key (dcl_...) via the Declaw API credential.

Docs: https://docs.declaw.ai
GitHub: [ GitHub - declaw-ai/n8n-nodes-declaw: n8n community node for Declaw — secure Firecracker microVM sandboxes for AI agents · GitHub ]
npm: n8n-nodes-declaw

Happy to answer questions or take feature requests — would love feedback from the community :folded_hands:

Shivam

Running AI-generated code in sandboxed microVMs is the right approach for agent workflows - especially with prompt injection defense built in. One use case this unlocks nicely: letting an AI agent write and run custom data transformation scripts per request, without needing to maintain a static Code node for every possible case. Will definitely be testing this for agent-driven ETL patterns.

1 Like