Skip to main content

Transfer credentials to other n8n instances using a multi-form

Workflow preview

Workflow preview
100%
Transfer credentials to other n8n instances 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 transfer credentials from one n8n instance to another. How it works A multi f...

Best for

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

Tools used

n8n-nodes-base.form, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.executecommand, n8n-nodes-base.readwritefile, n8n-nodes-base.extractfromfile, n8n-nodes-base.stickynote

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
Transfer credentials to other n8n instances using a multi-form
Workflow name
Transfer credentials to other n8n instances using a multi-form

Purpose

This workflow allows you to transfer credentials from one n8n instance to another.

How it works

  • A multi-form setup guides you through the entire process
  • You get to choose one of your predefined (in the Settings node) remote instances first
  • Then all credentials of the current instance are being retrieved using the Execute Command node
  • On the next form page you can select one of the credentials by their name and initiate the transfer
  • Finally the credential is being created on the remote instance using the n8n API. A final form ending indicates if that action succeeded or not.

Setup

  • Select your credentials in the nodes which require those
  • Configure your remote instance(s) in the Settings node
    • 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

  • Please note, that this workflow can only run on self-hosted n8n instances, since it requires the Execute Command Node.
  • 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 manage credentials across different environments.

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 - Success

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

Block 2 - Error

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

Block 3 - Create Credential

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

Block 4 - Get Instance Names

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

Block 5 - Settings

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

Block 6 - Export Credentials

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

Block 7 - Get Credentials Data

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

Block 8 - Binary to JSON

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

Block 9 - Get Credential Names

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

Block 10 - Choose Instance

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

Block 11 - Choose Credential

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

Block 12 - Prepare Request Data

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

Block 13 - Sticky Note6

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

Block 14 - Sticky Note

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

Block 15 - Sticky Note7

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

Block 16 - Sticky Note8

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

Block 17 - Sticky Note9

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

Block 18 - Sticky Note10

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

Block 19 - Sticky Note11

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

Block 20 - Sticky Note12

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

Block 21 - Sticky Note13

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

Block 22 - On form submission

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

3. Summary Table

Workflow Transfer credentials to other n8n instances using a multi-form
Complexity advanced
Nodes 22
Categories DevOps
Author Mario
Published 03 Nov 2024

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2521/2521.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 Transfer credentials to other n8n instances using a multi-form do?

Purpose This workflow allows you to transfer credentials from one n8n instance to another. How it works A multi f...

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.