n8n-autopilot

Writes or edits an n8n Decorator-TS .workflow.ts file from verified node contracts, or fixes a file from validation/wiring errors. The only file-writing agent in the build-workflow-v2 pipeline. Never validates or pushes — the orchestrator gates that.

Pulls an existing n8n workflow from the instance (or reads the local file) and returns a structured summary of its current shape — trigger, nodes, links, credentials, workflow id, sync status — plus where a requested change should apply. Read-only. Used as the comprehension phase of the build-workflow-v2 EDIT flow before patching an existing workflow.

Drift-aware deploy gate — checks remote sync status, then runs `npx n8nac push <file> --verify`. Never bypasses the push-gate hook, never runs `resolve`. Reports pushed/verified/workflowId/driftStatus. Used as the hard Deploy gate in build-workflow-v2 (greenfield + edit).

Keeps the local repo a complete mirror of the instance's workflows. Discovers remote workflows missing locally (`list --json`, remote-only status) and pulls them (`pull <id>`). Read-only on files (the n8nac CLI writes the pulled .workflow.ts). Used by the mirror-sync workflow that enforces the local-first invariant the edit flow relies on.

Produces the VERIFIED parameter contract for a single n8n node type by reading its real schema via `npx n8nac skills node-info --json`. Adversarial — omits any param key it is not certain exists, because n8n silently ignores wrong keys at runtime. Read-only. Used in the Research fan-out of build-workflow-v2 to kill the

EXPERIMENTAL deterministic builder for a whole n8n workflow STACK (multiple sub-workflows wired via Execute Workflow), JS-orchestrated. Takes a PRP-style end-to-end use case, decomposes it into sub-workflows along known rules, fixes the handover contracts between them, documents the architecture (mermaid) in one central file, then builds each sub-workflow bottom-up via build-workflow-v2. Two modes: GREENFIELD (new stack) and EXTEND (change an existing one). Decomposition rules, build order (topological), and per-sub-WF gates are JS control flow the model cannot skip. Use for multi-workflow use cases; for a single workflow use build-workflow-v2.

EXPERIMENTAL deterministic variant of build-workflow + deploy, JS-orchestrated. Two modes: GREENFIELD (new workflow) and EDIT (change an existing one). Phase ordering, gate-checks (validate / drift-safe push --verify), and fix-loop limits are enforced by a Claude Code JS Workflow script instead of prose — gates become if/while control flow the model cannot skip or short-circuit. Subagent roles live in agents/n8n-*.md. Use when you want hard-enforced discipline over the soft prose pipelines.

Full 3-phase pipeline (Research → Write+Validate → Deploy+Test) for shipping an n8n workflow end-to-end. Wraps Etienne's `n8n-as-code:n8n-architect` skill for schema research + authoring, adds repo-scoped orchestration — community-template lookup, validate-push-test loop, mcpTrigger publish gate, execution inspection, Completion Report.

Verify n8n-autopilot setup is functional — n8nac CLI present, workspace bound, n8n API reachable, companion plugin `n8n-as-code@n8nac-marketplace` enabled. Use after setup, after upgrading the plugin, or when commands behave unexpectedly.

Manage n8n DataTables (CRUD on tables, columns, rows) via the n8n public REST API. Use when the user wants to create/seed/list/delete data-table resources outside of a workflow — n8nac CLI does not support this. Curl is explicitly allowed for `/api/v1/data-tables` (carve-out in PreToolUse hook).

12 hooks across 3 events