Selectively import workflows from GitHub, including nested folders
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (12)
- n8n Form Trigger
n8n-nodes-base.formTrigger - GitHub
n8n-nodes-base.github - n8n
n8n-nodes-base.n8n - Extract from File
n8n-nodes-base.extractFromFile - n8n Form
n8n-nodes-base.form - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Split Out
n8n-nodes-base.splitOut - Merge
n8n-nodes-base.merge - Aggregate
n8n-nodes-base.aggregate
What it does
This template lets you selectively import n8n workflows from a GitHub repository, even when your repository uses deeply nested folder structures. Unlike most import workflows, this template does not load everything automatically. Instead, it: • Traverses all nested folders in your repository • Collects every workflow JSON file found • Dynamically generates a selection form • Allows you to choose exactly which workflows to load • Cleans incompatible fields for n8n API compatibility • Creates workflows directly in your instance This makes it ideal for users who: • Work across multiple n8n instances • Store workflows in structured GitHub directories (e.g. YYYY/MM/) • Want precise control over which workflows are restored • Manage staging, production, or client environments If you maintain workflows in GitHub and need controlled, selective imports, especially across structured folder hierarchies, this template is built for that use case.