n8n-subworkflows

n8n-subworkflows is a skill for Claude Code from czlonkowski/n8n-skills. It costs 121 tokens per session (4,730 once invoked), scanned A, a copy of n8n-subworkflows, MIT.

Guidance for making reusable n8n sub-workflows, which are smaller workflows that another workflow can call like a function in a program. They define inputs, perform shared work, and return an output.

In plain words
What is it for?
Extracting shared steps, building multi-step workflows, defining input and output rules, and choosing how one workflow calls another.
Why use it?
Copying the same steps into several workflows makes fixes easy to miss and versions drift apart. Sub-workflows keep shared logic in one place and make larger workflows easier to manage.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the n8n-mcp-skills plugin — 15 skills shipped together , and of n8n-mcp-skills

Good fit Extracting shared steps, building multi-step workflows, defining input and output rules, and choosing how one workflow calls another.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/czlonkowski/n8n-skills/n8n-subworkflows
About the project

n8n-skills is a collection of Claude Code skills and hooks that guide AI assistants in creating, validating, and deploying n8n workflows through the n8n-mcp server. Developers use it to automate workflow construction, configure nodes and expressions, resolve validation errors, and operate self-hosted n8n. The catalogue entries are its skills, hooks, plugins, and instruction.

czlonkowski/n8n-skills · 6,210 stars · on GitHub · n8n-skills.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add czlonkowski/n8n-skills --skill n8n-subworkflows
Clone the repo
git clone --depth 1 https://github.com/czlonkowski/n8n-skills

Made for: Claude Code.

Or install n8n-mcp-skills, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for n8n-subworkflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/n8n-subworkflows/github.svg)](https://agentmods.dev/skills/czlonkowski/n8n-skills/n8n-subworkflows)
Your own site
<a href="https://agentmods.dev/skills/czlonkowski/n8n-skills/n8n-subworkflows"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/n8n-subworkflows/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for n8n-subworkflows

Your own site · 80×15
<a href="https://agentmods.dev/skills/czlonkowski/n8n-skills/n8n-subworkflows"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/n8n-subworkflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 30 Aug 2026
  • Snyk pass 30 Aug 2026
How audits are shown
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00121 $0.04730
Opus 5 $0.00060 $0.02365
Sonnet 5 $0.00024 $0.00946
Haiku 4.5 $0.00012 $0.00473

Measured 11d ago against content hash 00eeee94733f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

n8n-subworkflows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to n8n-subworkflows — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/n8n-subworkflows/SKILL.md · 252 lines

How it starts

The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.

n8n Sub-workflows

A sub-workflow is a reusable function. An Execute Workflow Trigger declares typed inputs, the body does the work, and the last node returns the output. A caller invokes it through an Execute Workflow node like any other step.

That framing buys you the things functions buy you everywhere: encapsulation, reuse, testability, replaceability. It's the primary reuse mechanism in n8n, and it's badly underused. Without it, the same logic gets copy-pasted across workflows — then a bug gets fixed in two places, the third copy gets missed, and your "identical" copies quietly drift apart.

This skill is about when to reach for a sub-workflow, how to define its input/output contract so callers (and agents) can actually use it, how to call it correctly (all vs each, blocking vs fire-and-forget), and how to name it so it gets found instead of rebuilt.


The two non-negotiables

Everything else is judgement. These two are not.

1. Search before you build

Before you write logic for a generic problem, check whether a sub-workflow already does it. The community MCP can't filter workflows by tag, so the name is the discovery surface:

n8n_list_workflows()                          # scan the library
n8n_get_workflow({ id: "<candidate>" })       # read its inputs/outputs + body

If something fits, use it and tell the user ("I found Subworkflow: Parse RFC2822 date — using that"). If nothing fits, build it with a discoverable name so the next search finds it. The discovery convention (verb-first prefixes) lives in NAMING_AND_DISCOVERY.md.

2. The Execute Workflow Trigger uses "Define Below" with typed fields — not passthrough

The trigger has two input modes. Default to "Define Below" with explicit typed fields. Define Below is the only mode that gives callers a schema to fill — it's what lets an AI agent pass values via $fromAI and what lets structured callers map fields cleanly. Passthrough has no schema, so the trigger can't be wired as a clean agent tool and structured callers have nothing to bind to.

Read the full file on GitHub · 252 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 252 lines · 121 tokens per session scan A 00eeee94733f

Subscribe to this mod's changes

n8n-subworkflows is a skill published in the GitHub repository czlonkowski/n8n-skills (6,210 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 4,730 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to n8n-subworkflows, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

build-workflow

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…

neurawork-git/n8n-autopilot · 85 tokens

build-stack-v2

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…

neurawork-git/n8n-autopilot · 153 tokens

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…

neurawork-git/n8n-autopilot · 116 tokens

deploy

Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; --activate --prod runs production test). Side-effecting — only invoked explicitly via /deploy.

neurawork-git/n8n-autopilot · 47 tokens

session-env

Explain and verify how a Claude session pins itself (and all its n8nac workflow/instance commands) to exactly ONE n8n environment without clobbering other sessions' global active env. Use when the user asks "which env am I on", "how does session env pinning work", "pin this session to env X", "why was my env command…

neurawork-git/n8n-autopilot · 108 tokens

stack-intake

Guided interview that turns a rough idea into a PRP-style use-case description ready for /n8n-autopilot:build-stack-v2. Classic question-by-question format aimed at people NOT yet experienced with n8n — it asks about overall inputs, outputs, a concrete worked example, expected behavior, external systems, volume, and…

neurawork-git/n8n-autopilot · 146 tokens