# Importing a Workflow

> Bring a workflow into Glow from n8n or Make by importing its exported JSON.

Glow imports workflows exported from other automation platforms, so moving an existing automation across does not mean rebuilding it step by step.

**Supported sources: n8n and Make.**

## How to import

1. Export the workflow from your current tool as JSON. From n8n, that is the workflow's JSON. From Make, it is the scenario blueprint.
2. In Glow, open your workflow list and choose **Import JSON**.
3. Upload the file.

The dialog carries instructions for exporting from each supported platform, so you do not need to look them up separately.

Glow builds the canvas from the file: the steps, how they connect, and the configuration it can map. Anything without a direct equivalent in Glow is left for you to complete. That is normal when moving between platforms that model things differently.

> **Credentials never travel in an exported file**, from any platform. Every
> connection the workflow uses has to be authorised again in Glow before it will
> run. See [Connecting an App](/manage/apps-and-integrations/connecting-an-app).

## Sharing a workflow inside Glow

Inside Glow, a workflow moves as a template or a saved version rather than as a file. Use the route built for the job:

- **[Templates](/getting-started/templates/sharing-and-templates)**: publish a workflow so others can fork their own copy. This is how to share a pattern with your team or the wider community.
- **[Version history](/build/core-concepts/versioning)**: save a version before a risky change and restore it if the change goes wrong. This is what to reach for if you were thinking of exporting as a backup.

## What's Next?

- Plan a move from another platform with [Migrating to Glow](/getting-started/migrating-to-glow).
- Reconnect the credentials an import leaves empty in [Connecting an App](/manage/apps-and-integrations/connecting-an-app).