Skip to main content

Import workflows and map their credentials using a multi-form

Workflow preview

Workflow preview
100%
Import workflows and map their credentials using a multi-form preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Purpose This workflow allows you to import any workflow from a file or another n8n instance and map the credentials easily. ![Image](https://i.imgur.com/Mn...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.extractfromfile, n8n-nodes-base.executecommand, n8n-nodes-base.readwritefile, n8n-nodes-base.merge, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.noop

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mario.

Original n8n.io source

1.1 Workflow description

Title
Import workflows and map their credentials using a multi-form
Workflow name
Import workflows and map their credentials using a multi-form

Purpose

This workflow allows you to import any workflow from a file or another n8n instance and map the credentials easily.

How it works

  • A multi-form setup guides you through the entire process
  • At the beginning you have two options:
    • Upload a workflow file (JSON)
    • Copy workflow from a remote n8n instance
  • If you choose the second option, you get to choose one of your predefined (in the Settings node) remote instances first, then it retrieves a list of all the workflows using the n8n API which you then can choose a workflow from.
  • Now both initial options come together - the workflow file is being processed
  • In parallel all credentials of the current instance are being retrieved using the Execute Command node
  • The next form page enables a mapping of all the credentials used in the workflow. The matching happens between the names (because one workflow can contain different credentials of the same type) of the original credentials and the ones available on the current instance. Every option then shows all available credentials of the same type. In addition the user has always the choice to create a new credential on the fly.
  • For every option which was set to create a new credential, an empty credential is being created on the current instance using the n8n API. An emoji is being appended to the name, which indicates that it needs to be populated.
  • Finally the workflow gets updated with the new credential ID’s and created on the current instance using the n8n API. Then the user gets a message, if the process has succeeded or not.

Setup

  • Select your credentials in the nodes which require those
  • Configure your remote instance(s) in the Settings node. (You can skip this step, if you only want to use the File Upload feature)
    • Every instance is defined as object with the keys name, apiKey and baseUrl. Those instances are then wrapped inside an array. You can find an example described within a note on the workflow canvas.

How to use

  • Grab the (production) URL of the Form from the first node
  • Open the URL and follow the instructions given in the multi-form

Disclaimer

  • Security: Beware, that all credentials are being decrypted and processed within the workflow. Also the API keys to other n8n instances are stored within the workflow.
  • This solution is primarily meant for transferring data between testing environments. For production use consider the n8n enterprise edition which provides a reliable way to deploy workflows between different environments without the need of manual credential mapping.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Extract from File

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 2 - Export Credentials

Type / Role
n8n-nodes-base.executeCommand - executeCommand
Config choices
Version 1

Block 3 - Get Credentials Data

Type / Role
n8n-nodes-base.readWriteFile - readWriteFile
Config choices
Version 1

Block 4 - Binary to JSON

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 5 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 6 - Collect Credentials to Replace

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 7 - Settings

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Prepare Request Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Get Workflows

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - No Operation

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 11 - Determine Workflow Source

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 12 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Error1

Type / Role
n8n-nodes-base.form - form
Config choices
Version 1

Block 17 - Error

Type / Role
n8n-nodes-base.form - form
Config choices
Version 1

Block 18 - Split Out Workflows

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 19 - Get Workflow Names

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 20 - Sort by updatedAt DESC

Type / Role
n8n-nodes-base.sort - sort
Config choices
Version 1

Block 21 - No Operation1

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 22 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Rename Keys

Type / Role
n8n-nodes-base.renameKeys - renameKeys
Config choices
Version 1

Block 24 - Create Workflow

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Showing the first 24 of 58 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Import workflows and map their credentials using a multi-form
Complexity advanced
Nodes 58
Categories DevOps
Author Mario
Published 29 Oct 2024

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2506/2506.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Import workflows and map their credentials using a multi-form do?

Purpose This workflow allows you to import any workflow from a file or another n8n instance and map the credentials easily. ![Image](https://i.imgur.com/Mn...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.