Does n8n-as-code run?

Yes. n8n-as-code runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test n8n-as-code?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc7f42e8781c. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test n8n-as-code?

The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does n8n-as-code take to install?

20 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does n8n-as-code need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing n8n-as-code?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for n8n-as-code?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

n8n-as-code

Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.

Runssource: GitHub homepageTypeScriptMITcommit cc7f42e8781c

TypeScript, MIT licensed. The project labels itself: ai skills, claude, copilot, cursor, gitops, low code, n8n and ontology.

n8n-as-code runs. An Argusic agent installed it in 20 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install --ignore-scripts completes with warnings only, tsc -b TypeScript compilation succeeds, CLI version 2.7.0 responds to all commands, and 6 test suites pass (922 total tests, 0 failures across transformer, CLI, skills, MCP, openclaw, and vscode packages)
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.10 (measured)
recorded runs: 1
last tested: 2026-10-06
stars: 1,593
forks: 180
open issues: 21
watchers: 9
size: 84 MB
created: 2026-01-03
last push: 2026-10-03

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-06. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing n8n-as-code, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

skills fixture n8n-docs-complete.json had 0 pages, wrong categories format (array vs object), missing metadata fields, causing 4 docs-provider tests to fail5 minutes
skills package test script path '--workspace=@n8n-as-code/skills' hardcodes ../../node_modules/.bin/jest which doesn't resolve (jest is in packages/skills/node_modules/.bin/jest)3 minutes
npm install with scripts fails: plugins/openclaw/n8n-as-code/node_modules/openclaw preinstall script rejects Node 18 (requires >=22.22.3)2 minutes
cli-live integration tests fail: require a live n8n instance (no .env.test with real credentials)
CLI 'convert' command crashes with SyntaxError: node:util does not export styleText (needs Node >= 20.12)

Install time: 20 minutes
Cold machine to finish: 19 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: npm install --ignore-scripts exited 0; tsc -b succeeded; node packages/cli/dist/index.js --version returned 2.7.0; npm test on transformer (93/93 passed), cli (459/459 passed), skills (159/159 passed after fixes), mcp (37/37 passed), openclaw (11/11 passed), and vscode (163/163 passed); 'node packages/cli/dist/index.js workspace status --json' returned valid JSON with version=4
Model tokens used: 139,565
Exact commit tested: cc7f42e8781c
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 Test Files  3 passed (3)
      Tests  11 passed (11)
   Start at  22:34:09
   Duration  1.08s (transform 267ms, setup 0ms, collect 1.35s, tests 34ms, environment 1ms, prepare…
exec
/bin/sh -lc date in /work/repo
 succeeded in 0ms:
Tue Oct  6 22:34:19 UTC 2026
All verification is complete. Here's the final report:
tokens used
139,565
All verification is complete. Here's the final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Installed in 20 minutes.
Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.

What did not, or is not known

Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.10	2026-10-06 22:34 UTC

Topics (from GitHub)

ai-skills claude copilot cursor gitops low-code n8n ontology skills typescript vscode workflow-automation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/n8n-as-code.svg)](https://argusic.com/subject/n8n-as-code)

Questions

Does n8n-as-code run?: Yes. n8n-as-code runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test n8n-as-code?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc7f42e8781c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test n8n-as-code?: The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does n8n-as-code take to install?: 20 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does n8n-as-code need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing n8n-as-code?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for n8n-as-code?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.