Prerequisites
You need a running n8n instance:
- Self-hosted — Docker (
docker run n8nio/n8n), npm (npx n8n), or the official n8n Desktop app - Cloud — n8n.cloud (managed, free trial)
Both work identically for imports. New to n8n? The official quickstart takes about ten minutes.
Three import methods
Paste from clipboard
Click Copy JSON on any workflow detail page. In n8n, create a new workflow, click into the empty canvas, and paste with Cmd+V (Mac) or Ctrl+V (Windows / Linux). All nodes appear pre-wired.
Best for trying one workflow at a time.
Import from File
Click Download JSON on the workflow detail page (saves {slug}.json). In n8n: Workflows → Import from File, select the file. Same end result as paste, but you keep a local copy.
Best when you want a folder of n8n workflows in version control.
AutomationFlows desktop app
One-click install for macOS (Apple Silicon + Intel, signed and notarized) and Windows. Browse the full catalog inside the app, click Install, and the workflow is pushed straight to your local n8n instance via its REST API. Bulk-install entire vertical packs in one action.
Pro / Pro+ / Lifetime users — included with subscription. See pricing →
Step by step (clipboard method)
- Pick a workflow. Browse the catalog, filter by integration or category, and open a workflow detail page. You'll see the title, description, integration list, complexity score, and the full JSON.
- Copy the JSON. Click the
Copy JSONbutton at the top of the JSON block. The whole workflow definition lands on your clipboard. - Paste into n8n. In your n8n instance:
Workflows → Add workflow. Click into the empty canvas. PressCmd+VorCtrl+V. Nodes appear, already wired. - Add your credentials. Each integration node (Slack, OpenAI, Sheets…) shows a red icon — it needs credentials. Click the node, click
Create Newnext to Credentials, follow the OAuth or API-key flow. We strip credential IDs from every workflow before publishing, so you always start fresh here — never a leaked key from someone else. - Activate. Toggle the workflow active using the switch at the top right. For webhook-triggered workflows, copy the production webhook URL (visible after activation) into your upstream service. For cron / scheduled workflows, you're done — n8n fires on schedule. Click
Execute Workflowto test manually first.
What we strip before publishing
Workflow exports often contain test-run artifacts. Before any workflow lands in the catalog we remove:
| Field | Why we strip it |
|---|---|
pinData | Stored test inputs/outputs may contain real API responses, emails, or tokens |
credentials.{type}.id | Avoids leaking instance-specific credential UUIDs (the type stays so n8n knows what to ask for) |
webhookId (on trigger nodes) | Avoids leaking active webhook URLs from the original author's instance |
meta.instanceId | Fingerprint of the original n8n install — not yours to publish |
You'll never import a workflow that leaks someone else's API keys, webhook URL, or instance fingerprint. Read the full provenance & privacy policy →
Troubleshooting
"Node type X not recognized"
The workflow uses a community node not installed on your instance. Look up the package on npm, install via Settings → Community Nodes, restart n8n, retry import.
"Webhook URL doesn't fire"
Check that the workflow is active, not just saved. On n8n.cloud and self-hosted production, the production URL is different from the test URL — copy it from after the active toggle, not the editor preview.
"Credentials node shows error after import"
Expected — we strip credential IDs. Click the node, Create New credentials, follow OAuth / API-key flow.
Workflow won't paste into n8n
Some browsers block clipboard access on initial click. Try the Method 2 fallback: Download JSON → Import from File in n8n.
Workflow uses an integration I don't have access to
Many AutomationFlows workflows can be adapted by replacing one integration node (e.g. swap Slack for Discord) without rewriting the rest. The community is good at submitting variants — search the catalog for similar workflows on your stack.
FAQ
Where do imported workflows live?
Inside n8n's database (SQLite by default for self-hosted, Postgres for n8n.cloud). They appear in the Workflows list immediately after import — no filesystem path to manage.
Do I need to restart n8n after importing?
No. Workflows show up instantly. Only restart if you just installed a community node.
Are imports free?
Yes — every workflow can be copied for free, no signup required. Pro ($9/month or $299 lifetime) unlocks bulk JSON download, weekly digests, and integration-filtered alerts. Vertical packs ($99–$149) sold separately.
Can I trust workflows from the catalog?
Every workflow is integration-tagged, complexity-scored, and privacy-stripped. Source repo and original author are linked on every detail page. Always read the node graph before activating — workflows with code or function nodes execute JavaScript inside n8n.
How do I uninstall a workflow?
In n8n's Workflows list, click the workflow, click ⋯ in the top right, click Delete. Removed from your instance along with execution history. The desktop app (coming soon) will offer one-click uninstall directly from the catalog.
Do these workflows work on n8n.cloud?
Yes. Pure n8n JSON imports identically on n8n.cloud, self-hosted Docker, npm, or the official n8n Desktop app.