How to import workflows into n8n?

To import a workflow into n8n, you either paste the workflow JSON directly into the editor using the “Import from File” or “Import from Clipboard” options, or you upload the JSON file through the UI. n8n workflows are always stored as JSON, so importing simply means loading that JSON into the editor. This works the same whether you're in n8n Cloud, Desktop, or a self‑hosted instance.

 

Ways to Import a Workflow

 

You can import a workflow in n8n using three real and commonly used methods. All of them rely on the fact that n8n workflows are represented as JSON files. What you're really doing is loading this JSON into the n8n editor so it becomes an actual workflow in your workspace.

• Import from file: Upload a .json file that contains the workflow definition.
• Import from clipboard: Copy the raw JSON and paste it into the dialog box.
• API import: Send a request to the n8n REST API (/workflows) with the workflow JSON payload.

 

Detailed Explanation (Step-by-Step)

 

Below is a clear explanation suitable for someone new to n8n, but with the accuracy expected from production usage.

• Get the workflow JSON
  Every workflow in n8n is just a structured JSON document. If someone shared a workflow with you, they likely gave you a .json file or the JSON text itself.
• Open the n8n Editor UI
  This is the browser interface where you visually build and view workflows. It doesn’t matter if you're using n8n Cloud, Desktop, or a Docker deployment — the UI behaves the same.
• Use the Import option
  In the top-right corner of the editor, open the menu and choose Import from File if you have a file, or Import from Clipboard if you have raw JSON copied. n8n will validate the JSON and load the nodes into the canvas.
• Check credentials after import
  This is important in production. Credentials are never included in workflow JSON for security reasons. After import, nodes that require credentials (HTTP Request, MySQL, Google Sheets, etc.) will show a warning until you select or create the proper credential set.
• Save the workflow
  Importing loads it into the editor, but it is not saved until you click Save. You can also rename it at this point.
• Activate triggers only after verifying
  Triggers like Webhook, Cron, or App-based triggers become active only when the workflow is activated. Always review the workflow first to avoid unexpected executions in production.

 

Importing via API

 

This is how you import a workflow programmatically into a self‑hosted instance using the official n8n REST API. This is useful in CI/CD setups or when promoting workflows from staging to production.

curl -X POST https://your-n8n-domain.com/rest/workflows \
  -H "Content-Type: application/json" \
  -H "X-N8N-API-KEY: YOUR_API_KEY" \
  -d '{
    "name": "My Imported Workflow",
    "nodes": [],
    "connections": {}
  }'

 

This API endpoint expects the same JSON structure that the UI uses. After sending it, the workflow appears in the Editor UI immediately.

 

What Actually Happens Internally

 

When you import a workflow, n8n simply parses the JSON into its internal workflow model. The JSON contains:

• Nodes: Each with its parameters, type, and position on canvas.
• Connections: How data flows between nodes.
• Settings: Timeout, retry, and execution settings.

No triggers or external calls are executed during import itself — the workflow is inert until you activate it. This behavior is very intentional for safety in real production systems.