Importing an Automation

Import an n8n workflow or Make scenario export for the Workflow Assistant to rebuild as a Glow automation. Review and test the generated Steps before replacing your original automation.

At a glanceVerified in app · Oct 30, 2026

Use it to: Import an exported n8n workflow JSON or Make scenario blueprint into a new Draft automation
Find it: Automations → Import JSON (or MCP create_workflow + import_workflow)
Cost: Glow AI tokens via Import JSON in the app · 0 Step credits and 0 Glow AI tokens via MCP import_workflow
Limits: Direct JSON import supports n8n and Make · Up to 50 canvas operations (<= 512,000 characters) per MCP import call
Output: A new Draft automation with triggers, built-in Steps, AI prompts, and a canvas checklist note for third-party app actions
Instead: Migrating to Glow (/getting-started/migrating-to-glow) when rebuilding from Zapier or Power Automate or planning a zero-downtime cutover

Supported direct imports: n8n and Make. You can import in two ways:

Route	How it works	Cost
Import JSON in Glow	Open Automations → Import JSON, drop the `.json` file into Import workflow, check the summary, and click Build workflow.	Uses Glow AI tokens (Assistant build)
From your AI client over MCP	Ask your connected AI client to call `create_workflow` + `import_workflow` with the raw exported JSON (`<= 512,000` characters).	0 Glow AI tokens and 0 credits

An import places the trigger, Glow’s built-in Steps, AI Steps (carrying AI prompts and updating simple references), direct connections, and n8n sticky notes. It also adds a "Not imported" checklist note on the canvas for third-party app actions and branch routes to connect in your workspace. For the complete platform-by-platform guide (including Zapier and Power Automate), see Migrating to Glow.

Export JSON or BlueprintAutomations: Import JSONAssistant RebuildReconnect & Test in Draft

How to import

Export from n8n or Make

Export your n8n workflow JSON or Make scenario blueprint. Split very large workflows into smaller parts before importing.

Select the file in Glow

Open Automations → Import JSON, drop your .json file into Import workflow (or click Select file), and check the detected export summary.

Build and verify in Draft

Click Build workflow to generate the Steps with Glow AI tokens. Keep the automation in Draft, reconnect app accounts, verify every mapping, and test against test destinations.

Inspect exported JSON before sharing or importing it. A file may contain tokens or sensitive data pasted into ordinary fields, even when account credentials are stored separately. Remove those values and configure the required app connections in Glow. See Connecting an App.

Choose between working on the same automation, distributing a copy, and saving a recoverable version:

Team sharing: set the automation’s visibility for eligible teammates and share its link to work on the same automation. You do not need to publish a template.
Templates: publish to Marketplace so others can create their own copies. Marketplace publication is public, not team-only sharing. Review the template’s fields for sensitive content before publishing.
Versioning: save a version before a risky change and restore it if the change goes wrong. Use this when you need a backup before editing.

Verify it works

Run: Open Automations → Import JSON, select an exported n8n or Make .json file, and click Build workflow
You should see: Glow opens a new Draft automation containing the mapped Steps and any unmapped-item notes.

What’s Next?

Plan a move from another platform with Migrating to Glow.
Reconnect the credentials an import leaves empty in Connecting an App.