Selectively import workflows from GitHub, including nested folders — n8n Workflow

High complexity Trigger26 nodes🏷️ File Management👁 2 viewsby Stephen Anindo

Overview

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 • Creat

Nodes used

GitHubCode

Workflow Preview

Configure Repo Owner
Set your GitHub repository owner using the form field.
Keep:
• Field Name: `Repo Owner`
• Label: `Repo Owner`
• Type: `Dropdown`
Create Repository Form Data Structure
Builds the JSON for the dynamic repository selection fo
How it works 🧠 (Workflow Explanation)
This workflow lets you selectively import n8n workflows
Instead of recursion or mult
Create Workflow File Form Data Structure
Builds the JSON used to populate the Workflow Selection
This section:
• Splits the discovered repository files
• Creates dynamic SELECT_WORKFLOWS
Format Workflows
Prepares selected workflow files for safe import into n
This section:
• Verifies the file was successfully retrieved
• Removes fields incompatible with the n8n API
• Build
Structure Success Message
Formats the final result for each processed workflow by
How it works 🧠 (Cue Logic Explanation)
This section traverses a GitHub repository using a queu
It:
• Starts at the repository root
• Fetch
O
On form submission
Get repositories for an …
Get a file
C
Create a workflow
E
Extract JSON From File
S
Select Repos
S
Set Name and Data
R
Results
Initialise Loop State
I
If Has Next Page
Set Current Path
Process Directory Contents
List Files
N
No Operation, do nothing
S
Split Out All Workflows
S
Select Workflow(s)
S
Split Out Selected Workf…
G
Get Target Repo(s) Data
Strip Incompatible API F…
M
Merge Success and Failed…
Create JSON Repo Options
Create JSON Workflow Opt…
F
Found Matching Workflow?
A
Aggregate Repositories
A
Aggregate Selected Workf…
S
Set Repository Name and …
26 nodes28 edges

How it Works

  1. 1

    Trigger

    The workflow starts with a trigger trigger.

  2. 2

    Process

    Data flows through 26 nodes, connecting aggregate, code, extractfromfile.

  3. 3

    Output

    The workflow completes its automation and delivers the result to the configured destination.

Node Details (26)

GI

GitHub

github

#1
CO

Code

code

#2

How to Import This Workflow

  1. 1Click Download JSON button on the right to save the workflow file.
  2. 2Open your n8n instance. Go to Workflows → New → Import from file.
  3. 3Select the downloaded selectively-import-workflows-from-github-including-nested-folders file and click Import.
  4. 4Set up credentials for each service node (API keys, OAuth, etc.).
  5. 5Click Test Workflow to verify everything works, then activate it.

Or paste directly in n8n → Import from JSON:

{ "name": "Selectively import workflows from GitHub, including nested folders", "nodes": [...], ...}

Integrations

aggregatecodeextractfromfileformformtriggergithubifmergen8nsetsplitout

Get This Workflow

Download and import in one click

Download JSONView on n8n.io
Nodes26
Complexityhigh
Triggertrigger
Views2

Created by

Stephen Anindo

Stephen Anindo

@sanindo

Tags

aggregatecodeextractfromfileformformtriggergithubifmergen8nset

New to n8n?

n8n is a free, open-source workflow automation tool. Self-host it or use the cloud version.

Get n8n Free →

Related File Management Workflows

COCOGOHT+5
medium

Sync SharePoint to Google Drive via Supabase (n8n Workflow)

Eliminate manual file transfers and data silos with this enterprise-grade synchronization pipeline. This n8n workflow automates the heavy lifting of mirroring your Microsoft SharePoint document libraries to Google Drive while maintaining a robust audit trail in Supabase or Postgres. Designed for high-reliability environments, the automation utilizes a sophisticated delta-check logic: it fetches SharePoint metadata, compares it against your existing database records using the 'Compare Datasets' node, and identifies only new or modified files for processing. By leveraging the 'Split in Batches' node, the system handles large volumes of data without hitting memory limits, ensuring every document is securely downloaded via HTTP and re-uploaded to its destination. Once the transfer is verified, the workflow updates your database status in real-time, providing a transparent log of your synchronization history. This is an essential solution for organizations transitioning between cloud ecosystems or those requiring a redundant, cross-platform backup strategy. It effectively bridges the gap between Microsoft and Google ecosystems using Supabase as a high-performance state-management layer. **Common Use Cases:** - Automated Multi-Cloud Disaster Recovery: Maintain a real-time mirror of critical SharePoint corporate assets in Google Drive to ensure business continuity during service outages. - Cross-Departmental Collaboration: Automatically sync project documentation from an executive SharePoint site to a creative team's Google Drive folder for seamless cross-platform access. - Centralized Document Auditing: Use Supabase to track every file movement between ecosystems, creating a searchable metadata index for compliance and regulatory reporting.

Scheduled·15 nodes
FOGOGOHT+2
medium

Automate Threads Video Backups to Google Drive & Sheets

Streamline your social media asset management with this robust n8n automation designed for digital marketers and content creators. This workflow eliminates the manual effort of downloading Threads content by providing a seamless bridge between Instagram's text-based platform and your cloud storage. Once triggered via a simple form input, the automation utilizes a RapidAPI connection to fetch high-quality video assets, processes the binary data, and securely uploads the file to a designated Google Drive folder. Simultaneously, the workflow maintains a centralized audit log in Google Sheets, capturing essential metadata such as timestamps and file IDs. Built-in logic gates and wait nodes ensure API rate limits are respected and file transfers are verified before logging. This is an essential tool for agencies managing high volumes of social content who need a reliable, automated pipeline for content repurposing, archival compliance, or collaborative review processes. By centralizing your Threads media assets, you ensure your creative team has instant access to raw footage without the friction of manual downloads. **Common Use Cases:** - Automated Social Media Content Archiving for Compliance - Centralized Asset Library Syncing for Creative Agencies - Competitor Research and Video Content Benchmarking

Trigger·9 nodes