n8n asks you to wire up a canvas. flowwork lets you describe what you already know — your Claude Code agent writes the workflow as code, runs it in your workspace, and you keep an artifact you can actually read, review, and audit.
Both let you automate work. The difference is where the work lives and who does it: n8n is a visual automation server you click together and administer; flowwork is a code-native engine your agent authors and operates, co-located with your files and tools. If you hold the context worth automating and you're already working in Claude Code, that distinction is the whole story.
| flowwork | n8n | |
|---|---|---|
| Authoring | Code, written with you by Claude Code (the flowwork skill) | Visual drag-and-drop node canvas |
| Who operates it | Your Claude Code agent — authors, triggers, monitors, handles human-in-the-loop | You, in the web editor; plus schedules & webhooks |
| Agent ↔ workflow | The workflow can delegate back to the driving agent (the agent directive) | LLM & agent nodes call model APIs as steps |
| Your workspace (files, repo, devops, browser) | First-class — the agent operates your local workspace | Server-side; reaching your files needs custom / SSH nodes |
| Claude skills & slash-commands | Reusable inside workflows | — |
| Source of truth | Code — git history, diffs, PR review | Workflow JSON in n8n's database (export / import) |
| Footprint | Single binary + CLI on any laptop, VPS, or sandbox | Node server + web editor + database (self-host or cloud) |
| Visual builder | Read-only graph view in the console | Yes — the core experience |
| Prebuilt integrations | Connectors + anything Claude Code can do | Hundreds of prebuilt nodes (n8n's strength) |
| Determinism & resilience | Compiled graph: retries, backoff, leases, replay | Workflow engine with retries; less strongly typed |
| Best for | Context-rich domain experts & developers automating in Claude Code | No-code / low-code teams; broad SaaS glue |
A visual canvas feels approachable, but it's still a black box you can't diff, review in a pull request, or hand to a teammate with confidence. Once a workflow grows past a handful of nodes, the canvas is the complexity, just hidden.
With flowwork the artifact is code — and because Claude Code writes it with you, writing was never the barrier. You bring the context and the judgement; the agent produces a typed, versioned definition you can actually read, review, audit, and change in seconds.
n8n has AI and agent nodes: the workflow calls a model as a step. flowwork inverts that relationship. Your Claude Code agent is the operator that authors and runs the workflow, and a step can delegate back to that agent with the agent directive — to read your files, reason over a document, run a command, or drive a browser.
Your context lives in your files, docs, and repositories. flowwork runs right there in your workspace, so the agent can reach and operate it. n8n executes on a server, away from where your context actually is.
flowwork is a single binary plus a CLI. Drop it next to Claude Code on your laptop, a VPS, or an ephemeral sandbox and the two operate together — scriptable, disposable, no UI to babysit.
n8n is self-hostable, but even self-hosted it's a long-running server, a web editor, and a database you administer. That's the right shape for a shared team canvas; it's the wrong shape for an agent working in a sandbox.
We'd genuinely point you to n8n when:
flowwork is built for the opposite case: you have the context, you're working in Claude Code, and you want durable, auditable automation you own as code.
Free tier: 3 active workflows, 10 runs/day. No credit card.