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

n8n Workflow Cloner Between Instances

n8n Workflow Cloner Between Instances is a 14-node automation blueprint connecting n8n API. Inspect its trigger, execution graph, branches, and implementation requirements.

n8n API

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.

14

Nodes

15

Links

1

Run groups

Connected tools

1 integrations

  • n8n API

Canvas controls

Fit wide systems, then zoom into any run group.

n8n Workflow Cloner Between Instances execution lanes1 run groups containing 14 workflow nodes and 15 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTGET - Workflows. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 02GET - WorkflowsINTEGRATIONN8N1 IN / 1 OUTGET - Destination Workflows. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 02GET - Destination WorkflowsINTEGRATIONN8N1 IN / 1 OUTSplit Out Workflows. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Split Out WorkflowsTRANSFORMSPLITOUT1 IN / 1 OUTSplit Out Workflows1. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Split Out Workflows1TRANSFORMSPLITOUT1 IN / 1 OUTMerge Workflows. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04Merge WorkflowsDECISIONMERGE2 IN / 1 OUTCode. transform node, code. 1 incoming and 1 outgoing connections.STEP 05CodeTRANSFORMCODE1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 06Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTCREATE - Workflow. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 07CREATE - WorkflowINTEGRATIONN8N1 IN / 1 OUTn8n - GET - Projects. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08n8n - GET - ProjectsINTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit Out Projects. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 09Split Out ProjectsTRANSFORMSPLITOUT1 IN / 1 OUTFilter Project. decision node, filter. 1 incoming and 1 outgoing connections.STEP 10Filter ProjectDECISIONFILTER1 IN / 1 OUTSET Project ID. transform node, set. 1 incoming and 1 outgoing connections.STEP 11SET Project IDTRANSFORMSET1 IN / 1 OUTPUT - Workflow in Project. integration node, httpRequest. 1 incoming and 1 outgoing connections.OUTCOMEPUT - Workflow in ProjectINTEGRATIONHTTPREQUEST1 IN / 1 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.14 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

When clicking ‘Test workflow’

15 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    GET - Workflows

    Integration

    GET - Destination Workflows

    Integration

  3. Step 3

    Split Out Workflows

    Transform

    Split Out Workflows1

    Transform

  4. Step 4

    Merge Workflows

    Decision

  5. Step 5

    Code

    Transform

  6. Step 6

    Loop Over Items

    Integration

  7. Step 7

    CREATE - Workflow

    Integration

  8. Step 8

    n8n - GET - Projects

    Integration

  9. Step 9

    Split Out Projects

    Transform

  10. Step 10

    Filter Project

    Decision

  11. Step 11

    SET Project ID

    Transform

  12. Outcome

    PUT - Workflow in Project

    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