Skip to content
SkillModel-led4,611 tokens in use

n8n Sub-workflows

A guide to reusable n8n sub-workflows: typed Define Below inputs, all versus each mode, verb-first names, stateless or stateful design and fire-and-forget parallel runs.

6,686 stars on the repository MIT Licenseczlonkowski/n8n-skills · skills/n8n-subworkflows
/plugin install czlonkowski/n8n-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing n8n Sub-workflows costs

119tokens idle
4,611tokens in use
8,196tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure17/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance92
  • Community60
  • Maturity36
  • Momentum40

n8n Sub-workflows is a skill for Claude that treats a sub-workflow as a reusable function. An Execute Workflow Trigger declares typed inputs, the body does the work and the last node returns the output, which a caller invokes through an Execute Workflow node.

The skill covers when to extract logic, searching for an existing sub-workflow first, typed Define Below inputs, return contracts, the mode and waitForSubWorkflow settings, splitting by input shape and using a typed sub-workflow as an AI agent tool.

What You Get

  • A decision flow for whether a chunk of logic should become a sub-workflow
  • Rules for typed workflowInputs on the Execute Workflow Trigger, with the two exceptions for binary and zero inputs
  • Contract rules: describe inputs and outputs, return natural shapes, return ok and error for expected failures, freeze fields once callers exist
  • A table comparing mode all and mode each, and the waitForSubWorkflow setting
  • The N+1 pattern for sub-workflows with different input shapes
  • Reference files for naming and discovery and for sub-workflow patterns

Common Use Cases

  • Extracting parsing, retry or notification logic that several workflows repeat
  • Breaking up a workflow that has grown past ten or more nodes
  • Exposing a multi-step operation as an AI agent tool
  • Running many items in parallel with fire-and-forget calls and a Data Table to track them
  • Renaming a sub-workflow input without breaking its callers

What Makes It Unique

It is built around n8n’s limits: the MCP cannot filter workflows by tag, so naming is the search surface, and n8n does not error on an unknown input field, so a rename can break callers silently. It also explains that mode each with waitForSubWorkflow set to false is the only real parallelism, and it tells Claude to search the library before writing new logic.

Under The Hood

The skill is instructions and two reference markdown files, with no scripts. It tells Claude to use the n8n-mcp tools to list and read workflows, patch nodes and connections, validate, run isolated test executions with pinned data, read executions, and manage Data Tables, all against your n8n server. It can create and activate workflows there, and a fire-and-forget design makes sub-workflows run in the background.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers