Agent skill · AI & Agents

n8n-subworkflows

Build reusable n8n sub-workflows with typed inputs, all-vs-each execution, discoverable naming, and agent-tool exposure.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill n8n-subworkflows --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 20 KB
Bundled scripts: none
Declared author: Romuald Czlonkowski
Path: skills/n8n-subworkflows/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# n8n Sub-workflows ## When to Use Use this skill when shared or multi-step logic should become a typed reusable workflow, when an existing workflow is growing difficult to reason about, or when an agent needs a workflow exposed as a tool. Preserve authentication and authorization boundaries when extracting logic. Do not place credentials in inputs or returned data, declare state-changing behavior explicitly, and ask before running or activating a sub-workflow that sends, writes, deletes, or calls a billable external service. 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 inpu

What's inside
Steps it walks through
  1. When to Use
  2. The two non-negotiables
  3. 1. Search before you build
  4. Should this be a sub-workflow?
  5. Stateless vs. stateful (deliberately)
  6. Inputs and outputs as a contract
  7. Declaring typed inputs (Define Below)
  8. The contract rules
  9. The final Return node — the legitimate Set exception
  10. Calling sub-workflows: mode and waitForSubWorkflow
  11. mode: all vs each
  12. waitForSubWorkflow: true vs false
  13. The only true parallelization n8n offers
  14. Splitting by input shape (the N+1 pattern)
Ships with 2 files
  • references/NAMING_AND_DISCOVERY.md
  • references/SUBWORKFLOW_PATTERNS.md
More from agentic-awesome-skills
All skills →
About this skill
What does the n8n-subworkflows skill do?

Build reusable n8n sub-workflows with typed inputs, all-vs-each execution, discoverable naming, and agent-tool exposure.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill n8n-subworkflows --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going