Templates / Selectively import workflows from GitHub, including nested folders

Selectively import workflows from GitHub, including nested folders

Ready for 3.0

by Stephen Anindo ✓ · 150 views · created 2026-02-11 · File Management

Ready 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.

What this workflow does

This workflow has 26 nodes and runs when someone submits an n8n form (“Repo Loader”). Along the way it connects GitHub.

How it runs

Trigger: When someone submits an n8n form (“Repo Loader”).

  1. Get repositories for an organization (GitHub): work with organization
  2. Set Repository Name and URL (Edit Fields (Set)): sets 2 fields: repo_name, repo_url
  3. Aggregate: combines items into one
  4. Create JSON Repo Options (Code): runs custom JavaScript code
  5. Select Repos (n8n Form): shows the next form page
  6. Initialise Loop State (Code): runs custom JavaScript code
  7. If: checks a condition and branches into true / false
  8. Set Current Path (Code): runs custom JavaScript code
  9. List Files (GitHub): list (file)
  10. Create JSON Workflow Options (Code): runs custom JavaScript code

…plus 14 more steps. See the full node list below.

Services it uses

GitHub

Before you upgrade to n8n 3.0

Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.

Nodes used (12)

From the author

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…

Excerpt from Stephen Anindo's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.