Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Restore Workflows from GitHub to n8n

Restore Workflows from GitHub to n8n is a 12-node automation blueprint connecting GitHub, n8n. Inspect its trigger, execution graph, branches, and implementation requirements.

GitHubn8n

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

12

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • GitHub
  • n8n

Canvas controls

Fit wide systems, then zoom into any run group.

Restore Workflows from GitHub to n8n execution lanes1 run groups containing 12 workflow nodes and 13 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 2 OUTGlobals. transform node, set. 1 incoming and 2 outgoing connections.STEP 02GlobalsTRANSFORMSET1 IN / 2 OUTn8n - get all workflows. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 02n8n - get all workflowsINTEGRATIONN8N1 IN / 1 OUTGitHub - get all files. GitHub node, github. 1 incoming and 1 outgoing connections.STEP 03GitHub - get all filesGITHUBGITHUB1 IN / 1 OUTSet n8n existing workflows names. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set n8n existing workflow…TRANSFORMSET1 IN / 1 OUTMerge globals and files. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04Merge globals and filesDECISIONMERGE2 IN / 1 OUTGitHub - get each file. GitHub node, github. 1 incoming and 1 outgoing connections.STEP 05GitHub - get each fileGITHUBGITHUB1 IN / 1 OUTSet name and content. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Set name and contentTRANSFORMSET1 IN / 1 OUTMerge Github and n8n workflows - Keep only non existing workflows based on the name. GitHub node, merge. 2 incoming and 1 outgoing connections.STEP 07Merge Github and n8n work…GITHUBMERGE2 IN / 1 OUTIf workflow already exists. decision node, if. 1 incoming and 2 outgoing connections.STEP 08If workflow already existsDECISIONIF1 IN / 2 OUTn8n - create workflow. integration node, n8n. 1 incoming and 0 outgoing connections.OUTCOMEn8n - create workflowINTEGRATIONN8N1 IN / 0 OUTWorkflow name already exists. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEWorkflow name already exi…INTEGRATIONNOOP1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.12 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

On clicking 'execute'

13 Execution Links

  1. Start

    On clicking 'execute'

    Trigger

  2. Step 2

    Globals

    Transform

    n8n - get all workflows

    Integration

  3. Step 3

    GitHub - get all files

    Integration

    Set n8n existing workflows names

    Transform

  4. Step 4

    Merge globals and files

    Decision

  5. Step 5

    GitHub - get each file

    Integration

  6. Step 6

    Set name and content

    Transform

  7. Step 7

    Merge Github and n8n workflows - Keep only non existing workflows based on the name

    Decision

  8. Step 8

    If workflow already exists

    Decision

  9. Outcome

    n8n - create workflow

    Integration

    Workflow name already exists

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas