n8n-as-code
Build, validate, sync, and operate n8n workflows with AI from your editor or terminal.
The evidence shows explicit sync operations, promotion dry-run and no-push controls, separation of repository configuration from machine-local secrets, and API-key input through stdin. Integration tests further verify that MCP tokens are excluded from repository configuration and that deleting an instance removes its scoped secret, supporting full credit for sensitive-data handling and external-effect transparency. Least privilege and confirmation lose points because no runtime permission manifest, per-operation authorization model, or mandatory confirmation for each high-impact action is shown. Rollback relies mainly on Git, conflict resolution, and promotion bindings rather than demonstrated transactional reversal of remote changes. Dependency security is thin: version ranges, alignment checks, and private vulnerability reporting exist, but no lockfile, vulnerability scanning, supply-chain pinning, or documented remediation evidence is supplied. Independent-project status, copyright ownership, and upstream n8n/community attribution are explicit, justifying full source-attribution credit.
The README, command model, V4 configuration tests, CI build, and generated-skill consistency checks provide strong internal consistency. Dependency availability is substantially deducted because builds dynamically obtain the latest stable n8n material, CI runs npm install while explicitly noting that package-lock.json is ignored, and several Actions use moving major-version tags; the supplied static evidence therefore cannot establish repeatable access to identical dependencies. Failure handling includes explicit legacy-config rejection, missing-workflow and API failure paths, and actionable generated-file drift diagnostics. It is not full credit because several demonstrated errors remain generic, such as API Error and SyncManager Error.
The material covers VS Code, Cursor, Claude Code, generic agents, CLI, OpenClaw, external n8n instances, and managed local environments, with development, sync, validation, promotion, and debugging scenarios. Tool boundaries are clearly divided among n8nac env, workspace, and n8n-manager, while independence and n8n-version compatibility are stated. Trigger precision is deducted because the actual n8n-architect instructions are absent, so the review cannot establish how reliably the agent distinguishes read-only requests from push, activation, execution, or other consequential intents.
The README has clear quick starts, command groups, package responsibilities, and component relationships, while all four installation paths contain actionable commands. The MIT metadata and complete license text agree, earning full marks for information architecture, installation, and licensing. Naming loses a point because n8n-as-code, n8nac, n8n-manager, Agent Skills/MCP, and multiple plugin forms coexist, and the root bin name differs from the primary CLI name. Examples are extensive but no embedded FAQ is supplied. Compatibility, independence, and third-party workflow licensing are noted, but there is no comprehensive limitations section. Version 0.2.0, release scripts, and plugin-version consistency checks are visible, yet no changelog or upgrade history is included. Copyright, contribution, issue, and security-reporting paths identify maintenance channels, but the package author is blank, the security email is unspecified, and release ownership is not fully described.
The product emits version-controllable TypeScript workflows and supplies conversion, validation, explicit synchronization, conflict resolution, JSON status, and dry-run planning, making outputs practically usable on the face of the source. Combining node knowledge, template search, typed editing, and multi-environment promotion offers clear marginal value over manually maintaining n8n JSON. Cost-benefit loses a point because the full build requires Node 22, a multi-package toolchain, a dynamic n8n cache, documentation downloads, and generation steps, while the costs of running, upgrading, securing, and credentialing n8n are not quantified. The stated 537-node and 7,700-plus-template scale is also not directly substantiated by the supplied files.
Many claims map to concrete commands, package descriptions, CI checks, and configuration integration tests. Secret separation, V4 persistence, deletion cleanup, and generated-skill consistency are corroborated across README, tests, and CI, supporting strong cross-source corroboration. Claim traceability is deducted because the 537-node and 7,700-plus-template figures, along with broad safety claims, lack supplied static inventories or count checks, and CI badges cannot prove that this revision passed during this review. Facts and qualifications are generally distinguished, including independence and compatibility advice, but promotional phrases such as safely, full n8n development workspace, and grounded lack precise definitions or demonstrated coverage.
- This assessment uses only the supplied static files; no build, test, plugin, CLI, or live n8n operation was executed.
- Before using push, promote, activate, run tests, tunneling, or instance deletion in production, verify the target environment, permission scope, credential isolation, backups, and recovery procedure.
- Dependency installation lacks a committed lockfile and the build fetches dynamic n8n material; pin dependencies and upstream versions and perform vulnerability and supply-chain review before deployment.
- Do not rely on the README alone for the 537-node, 7,700-plus-template, or broad safety claims; inspect revision-specific generated assets, inventories, and coverage tests.
- The project targets the latest stable n8n release; older instances may produce generation or validation mismatches and should be checked in an isolated environment first.
- The publisher is not verified by the FollowAgents enterprise registry. This means identity is unknown, not suspicious; independently verify repository signatures, release provenance, and maintenance channels.
What does this agent do, and when should you use it?
n8n-as-code is a development and operations toolkit composed of a VS Code/Cursor extension, the n8nac CLI, portable Agent Skills, n8n-manager, and a TypeScript transformer. It turns a repository into an n8n workspace where people and AI assistants can inspect node knowledge, edit workflows, validate them, and explicitly synchronize them with a selected n8n environment. Workflows can be stored as readable .workflow.ts files, reviewed through Git, and pushed to remote or locally managed n8n instances. Repository-level environment configuration is separated from API keys, managed-instance state, and other machine-local data. It is a strong fit for teams that want code review, controlled environment promotion, and editor-native n8n operations, provided they can keep their n8n version aligned with the latest stable schemas bundled by the project.
A user defines either a remote n8n URL or an n8n-manager instance with n8nac env add, stores an API key with n8nac env auth set, and selects the active target through n8nac env use. n8nac update-ai generates agent context containing schemas, examples, node knowledge, and validation guidance; n8nac skills search, node-info, and validate expose template discovery, node information, and workflow checks. Synchronization is deliberate: n8nac list discovers workflows, pull imports one into the repository, push --verify validates and sends a file to n8n, and resolve handles conflicts. promote moves one workflow or all .workflow.ts files between environment workflowsPath directories, rewrites target project metadata, maps credentials and supported Execute Workflow references, and records stable bindings in n8nac-promotion.json; --dry-run produces the create/update plan without writing or pushing. @n8n-as-code/transformer converts between n8n JSON and TypeScript classes built with @workflow, @node, and @links, while the VS Code/Cursor extension supplies a sidebar, canvas, environment controls, and an integrated Agent Workbench.
- An automation engineer working in VS Code or Cursor who wants to browse, edit, validate, and synchronize live n8n workflows without leaving the editor.
- A team bringing n8n assets under Git review that needs explicit pull and push operations, readable diffs, and conflict-resolution commands.
- A platform team promoting workflows from Dev to Prod that wants a dry-run plan before credential mappings, project metadata, and sub-workflow references are changed.
- A developer asking an AI assistant to create n8n workflows who needs grounded node schemas, examples, templates, and validation rules rather than model memory alone.
- An n8n user who prefers code-shaped assets and wants to convert workflow JSON into editable .workflow.ts classes for human or agent maintenance.
- A developer needing a local n8n sandbox who wants n8n-manager to control instance and tunnel lifecycles while n8nac remains the repository environment source of truth.
What are this agent's strengths and limitations?
- The bundled knowledge covers 537 nodes with full schemas and more than 7,700 templates, giving generation and validation concrete n8n context.
- It offers an editor extension, CLI, portable skills, an OpenClaw plugin, and a transformer, supporting both interactive work and terminal automation.
- Explicit synchronization, push verification, conflict handling, and promotion dry-runs provide review points before remote state changes.
- TypeScript workflows expose @workflow, @node, and @links structures that are easier to review and edit than raw workflow JSON.
- Environment promotion handles target project metadata, credential mappings, and supported Execute Workflow references instead of merely copying files.
- The bundled node schema targets the latest stable n8n release, so older instances may produce generation or validation mismatches and require upgrades.
- Remote operation requires network access and an n8n API key; managed local operation adds n8n-manager and machine-level instance lifecycle concerns.
- The Claude Code plugin is labeled Beta / Pending Review, so it should not be treated as a fully mature, formally reviewed integration.
- Promotion rewrites metadata and maps credentials and workflow references; even with dry-run support, complex environments require human review.
- This is an independent community project with no affiliation, endorsement, or sponsorship from n8n, which may matter to teams evaluating support risk.
How do you install or deploy this agent?
For the editor route, install etienne-lescot.n8n-as-code from the VS Code Marketplace or Open VSX, open a folder or .code-workspace, open the extension configuration, and create or select an n8n environment. For CLI use, the documented commands run through npx:
npx --yes n8nac env add Dev --base-url https://n8n.example.com --workflows-path workflows/dev
printf '%s' "$N8N_API_KEY" | npx --yes n8nac env auth set Dev --api-key-stdin
npx --yes n8nac env use Dev
npx --yes n8nac update-aiThis remote path requires a reachable n8n URL and N8N_API_KEY. To attach an existing locally managed instance, first run n8n-manager instance list, then:
npx --yes n8nac env add Local --managed-instance <id> --workflows-path workflows/local
npx --yes n8nac env use LocalThe Claude Code delivery is labeled Beta / Pending Review and uses:
/plugin marketplace add https://github.com/EtienneLescot/n8n-as-code
/plugin install n8n-as-code@n8nac-marketplaceHow do you use this agent?
Check that the selected environment is ready, then list its workflows:
npx --yes n8nac env status --json
npx --yes n8nac listPull a workflow, edit it, validate it, and push it explicitly:
npx --yes n8nac pull <workflow-id>
npx --yes n8nac skills validate workflows/dev/my-workflow.workflow.ts
npx --yes n8nac push workflows/dev/my-workflow.workflow.ts --verifyPreview an environment promotion before making changes:
npx --yes n8nac promote --from Dev --to Prod --dry-runAfter reviewing the plan, remove --dry-run to perform the normal file processing and push. Convert an existing JSON workflow with n8nac convert workflow.json --format typescript, or convert a directory with n8nac convert-batch workflows/ --format typescript. Pulls and pushes are never implicit; synchronization occurs only when requested.
How does this agent compare with similar options?
Compared with maintaining workflows only in the n8n interface, n8n-as-code adds a repository-resident TypeScript representation, explicit pull/push operations, Git diff review, conflict handling, and environment promotion. Within the toolkit, the VS Code/Cursor extension supplies the visual workspace and Agent Workbench, n8nac owns repository environments, validation, and synchronization, while n8n-manager is limited to local instances, Docker lifecycle, tunnels, secrets, and other machine-local operations; it is not the workspace source of truth.