How to Install Nod on Windows
Yes, Nod runs on Windows — you download the x64 installer, run it, choose Get started on the Welcome screen, and setup takes about 10 minutes. But go in with the right expectation: the Windows build is a research preview, not a finished product. This guide covers what the preview label actually means in practice, the WSL piece you need to know about before installing, the steps, and the version-specific update trap that catches early Windows users.
On a Mac instead? Use the Mac install guide. New to Nod entirely? What is Nod explains what you're installing.
Read this first: what "preview" means here
Nod as a whole is a research preview from n8n Labs, and the Windows and Linux builds are explicitly labelled preview in the official docs. In practical terms:
- Expect rough edges and fast change. Features shift between releases, and the docs themselves flag platform-specific quirks (the update behaviour below is one of them).
- Keep updates working. Because the build is moving quickly, staying current matters more than usual — see the gotcha section before you rely on auto-update.
- One owner per install. Each Nod installation belongs to a single person; sharing one Nod across a team is on the roadmap, not available yet.
- It can make mistakes. n8n is upfront that Nod is an experiment: its safety check is a model's judgement and can be wrong, which is precisely why it asks before acting on anything your request didn't cover. Treat the preview accordingly — supervise money-moving and message-sending jobs until you trust it.
- It only runs while your PC is awake. Like the Mac version, Nod pauses when the machine sleeps and stops entirely when the app is closed — scheduled jobs included. If you need an agent that works overnight, an always-on machine or a self-hosted server is the better home for it today.
None of that makes the Windows build a bad choice for trying Nod out. It just means you should install it as an experiment, not as load-bearing infrastructure.
System requirements
- Windows 11. The desktop installer is an x64 build.
- WSL 2 available. This is the part Windows users don't expect: per the official install docs, Nod's "private computer" — the sandboxed machine it works in — runs as a WSL distribution named
nod-<profile id>on Windows. If WSL isn't enabled on your PC yet, you'll need it in place for the local assistant to work. - A few GB of free disk space for the app and the runtime it downloads during setup.
- A model account for afterwards. An API key from a provider, or a ChatGPT Plus/Pro plan to sign in with. Nod does nothing until a model is connected — see Connect a model.
- No Node.js, Docker, or developer tools. Those are only needed for the run-from-source route, not the desktop app. You also don't need an n8n account: Nod is a standalone app.
Where Nod keeps things on Windows
Two details from the official install docs worth knowing before you go poking around your system:
- App data lives in
%APPDATA%\nod\profiles\local. - The private computer is that WSL distribution (
nod-<profile id>). It is Nod's workspace, not clutter — removing it in WSL removes the environment Nod works in. - Saved secrets are encrypted with Windows DPAPI, the standard Windows data-protection mechanism, rather than stored in plain text.
- Everything else stays on this PC too. Per the docs, Nod's database, files, memory, and saved logins all live on the machine running it — the Windows app is a local assistant first, not a cloud account with a desktop skin.
Install steps
- Download the Windows x64 installer (the latest version) from the Nod site (nod.n8n.io) or the releases page of the
n8n-io/nodGitHub repository. - Run the installer and complete the installation.
- Open Nod. On the Welcome screen, choose Get started to set up the local assistant on this PC, or Connect to a server if you already run Nod on another machine or server.
- Let Nod download its runtime and prepare the WSL-based private computer. Per the official docs, the full setup takes about 10 minutes.
- Connect a model in Settings → Models — this guide walks through the sign-in and API key options.
- Connect your email and calendar in Connect apps so Nod has something real to work on.
Preview gotchas
The early-build update trap. This is the big one, straight from the official install docs: Windows builds before 0.7.0 cannot update themselves, and builds 0.6.2 and earlier cannot install updates on Windows at all. If you installed one of those early builds, auto-update will never rescue you — download the latest installer manually once and install it over the top. From a current build onward, updates behave normally: Nod checks at launch and every 6 hours and downloads updates in the background.
Setup stalls while preparing the private computer. Check WSL first. Nod's workspace is a WSL distribution that it creates and manages itself — you don't need to set up a Linux environment by hand — but WSL itself has to be installed and working on the PC for that to happen. If WSL is missing or broken, fix that before reinstalling Nod.
"It stopped mid-task" usually means the PC slept. Nod has no background service that survives sleep or the app being closed. If a scheduled job didn't fire, check whether the machine was awake and Nod was open before suspecting the job itself.
Preview means the docs are your friend. Because the Windows build is young, behaviours can differ from the Mac build and change between releases. When something looks off, the official install docs track the known platform quirks — and our FAQ collects the common questions in one place.
After install
- Getting started — run your first real task in about ten minutes.
- Full tutorial — the complete walkthrough, including the safety and spending guardrails to set before you delegate anything serious.
- Nod hub — every guide in this series.