Move n8n workflows between instances without manual rebuilds. Guided forms help you pick a source, choose a workflow, map credentials, and create it on the target. Ideal for teams that promote workflows from dev to test to production.

The flow starts from a form submission. You can fetch workflows from a remote n8n instance using its base URL and API key, or upload a workflow JSON file. It lists workflows and sorts them by last update so you can pick the right one. It scans all nodes, finds used credentials, removes duplicates, and maps them by name. It exports local credentials with the n8n CLI, creates empty placeholders for missing ones, replaces credential links in the workflow, and then creates the final workflow on the target. You get clear error and success pages.

Setup needs instance details in a Settings node with name, apiKey, and baseUrl. Protect the forms with Basic Auth if needed. You need API keys for each source instance and permission to run the n8n CLI for credential export. Expect faster migration, fewer errors, and consistent credential mapping. Great for teams moving work across environments or merging workspaces.

• Form based steps collect the source type, instance, and workflow selection with optional Basic Auth protection.
• Remote instance picker uses a settings list of names, base URLs, and API keys.
• HTTP request to the n8n API pulls workflows with an API key header and a 250 item limit.
• Sort and split logic shows the most recently updated workflows first.
• File upload path accepts a workflow JSON and converts it from binary to JSON.
• Node scan finds all used credentials and removes duplicates by name.
• n8n CLI export gathers local credential data for mapping and comparison.
• Creates empty credentials when a required credential does not exist on the target.
• Replaces credential references inside the workflow before creating it on the target instance.
• Clear success and error forms confirm results and help with troubleshooting.

• Reduce workflow migration time from hours to minutes
• Automate up to 90% of credential mapping by name
• Cut credential related errors by up to 80%
• Handle lists of up to 250 workflows per request
• Connect multiple n8n instances with one guided flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with n8n. See the Tools Required section above for links to create accounts with these services.
3. Open the Settings node and add your remoteInstances list with name, apiKey, and baseUrl values. Use the example in the note to match the required format.
4. Create an n8n API credential for your target instance: double click the Create Workflow node, open the 'Credential to connect with' dropdown, click 'Create new credential', then follow the on screen steps to paste your n8n API key and base URL.
5. Repeat the same credential setup for the Create Empty Credentials node so both nodes point to the correct target instance.
6. Secure each Form node if needed: open the form node, enable Basic Auth, and set a username and password. Repeat for Choose Instance, Choose Workflow, Upload File, and Map Credentials forms.
7. Test the remote instance connection: run the workflow, open the Choose Instance form URL, pick an instance, and confirm the workflow list loads. If you see 401 errors, check the API key and base URL.
8. If you plan to use the credential export step, make sure the n8n CLI is available and the Execute Command node has permission to run. In container setups, allow the command or run this on a host where n8n CLI is installed.
9. Validate mapping: choose a workflow, review the listed credentials, and confirm suggested name matches. Add or edit mappings where needed, then continue.
10. Finish and verify: after creation, check the Success screen and confirm the new workflow exists on the target instance. Run a small test to ensure credentials resolve correctly.
11. Troubleshoot common issues: 404 or empty list usually means a wrong base URL path, 401 means an invalid API key, and file upload errors can be caused by size or invalid JSON.