# How to Import Workflows into n8n

- Tool: n8n
- Difficulty: Beginner
- Time required: 5 minutes
- Compatibility: n8n 0.170+ (self-hosted, Docker, n8n Cloud)
- Last updated: March 2026

## TL;DR

Import workflows into n8n using the editor UI or the CLI. In the UI, go to the menu and select Import from File or Import from URL. For bulk imports, use the n8n import:workflow CLI command. If you see a 'Could not find property option' error, the workflow was exported from a different n8n version and may need node updates.

## How to Import Workflows into n8n

Importing workflows lets you restore backups, share automations between n8n instances, and use community-built workflow templates. n8n workflows are stored as JSON files that describe all nodes, connections, and configuration. You can import them through the browser-based editor or the command-line interface. The process is straightforward, but version mismatches between the exporting and importing n8n instances can cause compatibility issues that need to be resolved after import.

## Before you start

- A running n8n instance (self-hosted or n8n Cloud)
- A workflow JSON file or URL to import
- For CLI imports: terminal access to the n8n server

## Step-by-step guide

### 1. Import a workflow from a file in the UI

Open the n8n editor in your browser. Click the menu icon (three dots or hamburger icon in the top bar) and select Import from File. A file picker dialog opens — select the JSON file from your computer. n8n loads the workflow into a new canvas. Review the nodes and connections, then click Save to keep the workflow. If any nodes show warnings, they may need updated credentials or configuration.

**Expected result:** The imported workflow appears in the editor with all nodes and connections intact. The workflow is saved with a new workflow ID.

### 2. Import a workflow from a URL

If the workflow JSON is hosted online (e.g., on GitHub, a gist, or a community forum), you can import it directly by URL. Click the menu icon and select Import from URL. Paste the URL to the raw JSON file. n8n downloads and loads the workflow. This is useful for importing shared community workflows or templates from the n8n workflow library.

**Expected result:** n8n fetches the JSON from the URL and loads the workflow into the editor. Save it to keep it in your instance.

### 3. Import workflows using the CLI

For self-hosted n8n, the CLI provides a bulk import command. This is the fastest way to restore multiple workflows from a backup. Each JSON file in the specified directory is imported as a separate workflow. Existing workflows with the same ID are updated.

```
# Import a single workflow
n8n import:workflow --input=./my-workflow.json

# Import all workflow files from a directory
n8n import:workflow --input=./backups/workflows/

# Docker: import a workflow into the container
docker cp ./my-workflow.json n8n:/tmp/my-workflow.json
docker exec n8n n8n import:workflow --input=/tmp/my-workflow.json
```

**Expected result:** The workflows are imported into n8n's database. They appear in the workflow list in the editor. Existing workflows with matching IDs are updated.

### 4. Handle version compatibility issues

If you see errors like 'Could not find property option' or nodes showing as 'Unknown', the workflow was exported from a different n8n version. Some nodes change between versions — parameters get renamed, node types get updated, or options get added/removed. To fix this, open each problematic node, review the settings, and reconfigure any missing or changed parameters. You may also need to replace deprecated nodes with their updated versions.

```
// Common version mismatch indicators:
// 1. "Could not find property option" — a dropdown option was renamed or removed
// 2. Unknown node type — the node was added in a newer version or removed
// 3. "Parameter X is not valid" — the parameter was renamed

// Fix: Open the node, check each parameter, and update to match
// the current version's options. Or update n8n to match the
// version the workflow was exported from.
```

**Expected result:** After fixing version-specific settings, all nodes show green (valid) status. The workflow can be executed without errors.

### 5. Reconnect credentials after import

Imported workflows reference credentials by ID, but credential IDs are specific to each n8n instance. After importing, open each node that requires credentials and select or create the appropriate credential. The workflow will not execute until all credential references are resolved. This is a security feature — credentials are never included in exported workflow files.

**Expected result:** All nodes show valid credential connections. The credential selector in each node shows the correct credential, not 'No credential' or a warning.

## Complete code example

File: `bulk-import-workflows.sh`

```bash
#!/bin/bash
# bulk-import-workflows.sh
# Import multiple n8n workflows from a backup directory

set -euo pipefail

BACKUP_DIR="${1:-./backups/workflows}"
LOG_FILE="./import-log.txt"

if [ ! -d "$BACKUP_DIR" ]; then
  echo "ERROR: Directory $BACKUP_DIR does not exist"
  exit 1
fi

# Count workflow files
FILE_COUNT=$(find "$BACKUP_DIR" -name '*.json' -type f | wc -l)
echo "Found $FILE_COUNT workflow file(s) in $BACKUP_DIR"
echo "Import started at $(date)" > "$LOG_FILE"

# Import each workflow file
SUCCESS=0
FAILED=0

for file in "$BACKUP_DIR"/*.json; do
  if [ -f "$file" ]; then
    FILENAME=$(basename "$file")
    echo "Importing: $FILENAME"

    if n8n import:workflow --input="$file" 2>> "$LOG_FILE"; then
      echo "  OK: $FILENAME" | tee -a "$LOG_FILE"
      ((SUCCESS++))
    else
      echo "  FAILED: $FILENAME" | tee -a "$LOG_FILE"
      ((FAILED++))
    fi
  fi
done

echo ""
echo "Import complete: $SUCCESS succeeded, $FAILED failed"
echo "Import finished at $(date)" >> "$LOG_FILE"
echo "Results: $SUCCESS succeeded, $FAILED failed" >> "$LOG_FILE"
```

## Common mistakes

- **Trying to execute an imported workflow without reconnecting credentials** — undefined Fix: Open each node that uses credentials, click the credential dropdown, and select or create the appropriate credential.
- **Importing a workflow from a newer n8n version into an older one** — undefined Fix: Update your n8n instance to match or exceed the version the workflow was exported from, or manually fix incompatible node settings.
- **Using the GitHub page URL instead of the raw file URL for Import from URL** — undefined Fix: On GitHub, click the Raw button to get the direct URL to the JSON content. The regular GitHub page URL returns HTML, not JSON.
- **Importing workflows with the same ID and accidentally overwriting existing ones** — undefined Fix: The CLI import with --input updates existing workflows that share the same ID. Back up your workflows first, or use the UI import which always creates new workflows with fresh IDs.

## Best practices

- Always review imported workflows before activating them — check node configurations and credentials
- Use the same n8n version on both the source and destination instances to avoid compatibility issues
- Reconnect all credentials after importing — credential secrets are never included in workflow exports
- Test imported workflows with the Test Workflow button before activating them for production use
- Keep a record of which workflows were imported and from which source for auditability
- Back up your existing workflows before importing to avoid accidentally overwriting them
- When sharing workflows publicly, remove any hardcoded values like API endpoints or email addresses

## Frequently asked questions

### Can I import workflows into n8n Cloud?

Yes. Use the UI method: open the editor, click the menu icon, and select Import from File or Import from URL. The CLI method is not available on n8n Cloud since you do not have terminal access.

### Does importing a workflow include the credentials?

No. Workflow exports never include credential secrets for security reasons. After importing, you must manually reconnect or create all credentials used by the workflow.

### What does 'Could not find property option' mean?

This error occurs when a node parameter references a dropdown option that does not exist in your version of n8n. The workflow was likely exported from a different version. Open the affected node and select a valid option from the dropdown.

### Can I import a workflow from n8n v0.x into n8n v1.x?

Usually yes, but some nodes were significantly changed in n8n 1.0. After importing, check for deprecated nodes (shown with warnings) and replace them with their updated versions.

### Will importing a workflow overwrite my existing workflows?

In the UI, importing always creates a new workflow with a fresh ID. With the CLI, importing a workflow that has the same ID as an existing one will update (overwrite) the existing workflow.

### Can RapidDev help migrate and import workflows between n8n instances?

Yes. RapidDev can handle full n8n migrations, including workflow imports, credential configuration, version compatibility fixes, and testing. Contact RapidDev for assistance.

---

Source: https://www.rapidevelopers.com/n8n-tutorial/how-to-import-workflows-into-n8n
© RapidDev — https://www.rapidevelopers.com/n8n-tutorial/how-to-import-workflows-into-n8n